Define `github` practices
Open
@jdhoffa is already working on this.
Since Feb 12, 2024.
git(hub)
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This may include:
- PR workflow used (e.g. git-flow, github flow, OR just allowing it to be at the maintainer's discretion)
- Expectations on the size and focus of a PR
- Expectations on being prudent with our GH minutes (maybe not important with all public repositories, but I'm thinking something like "test before commit" and "check before push" on our R packages)
- Merge strategies see #17
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.