🅿️⛱️ onboard checklist for new projects under org umbrella
@OpenINFbot is already working on this.
Since Feb 27, 2024.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 23h 54m
- Merged PRs (30d)
- 29
Description
[!TIP]
Compared to the now-stalled #716 re: issue & PR labels, #723 takes precedence
Here's why: the canonical storage location for our standard project label packs happen to be provided by the solution we have chosen for managing default github repo settings; namely the GitHub App simply named "Settings", which syncs repository settings defined in .github/settings.yml to GitHub, enabling Pull Requests for these now-serialized repository settings.
i have been meaning to do this for a very long time:
every project repo transferred under @OpenINF umbrella has to undergo a certain procedure before we can properly maintain it or bring it up to a recovered state where we may begin to place within the context of our project lifecycle(s); let us flesh that out (minimally at first, then more-so in the short-term)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.