discuss optimal merge strategies and PR guidelines
Open
Nobody has claimed this yet.
documentation
- Dominant language
- R
- Stars
- 171
- Forks
- 26
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 3
Description
It could be beneficial to discuss different merge strategies as well as expectations from contributors regarding commits and PRs. Having every single commit in git history might create clutter or squashing too much can make it hard to find important details. What would be your ideal strategy?
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.
Research direction
Start by locating any existing contributor and pull-request guidance in the repository. Compare its treatment of merge strategies, commit history, and squashing with the questions in this issue, then document an agreed policy and confirm that the guidance covers both commits and pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100