Add documentation around common git operations for the project
Open
Nobody has claimed this yet.
misc
upstream
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
- Upstreaming our patches
- Merging trunk into our fork to update it
- Patching the list of expected warnings
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 reviewing the project's existing documentation and maintenance guidance to find the appropriate location for these instructions. Document upstreaming patches, merging trunk into the fork, and updating the expected-warnings list; done means all three operations have clear, usable guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100