OpenINF / OpenINF/.github

🅿️⛱️ onboard checklist for new projects under org umbrella

Open
#723 4 comments 0 reactions 2 assignees View on GitHub

@OpenINFbot is already working on this.

Since Feb 27, 2024.

🏗️ Category: Infrastructure/Tooling/Builds/CI 📖 Category: Documentation 📝 Category: Content 🔔 Type: New
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.