Documentation: Mention `.git-blame-ignore-revs` somewhere
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 446
- Forks
- 32
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 1
Description
Because it's useful and no one seems to know about it
https://bsky.app/profile/simonpcouch.com/post/3luqioffers2t
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 the repository's documentation entry point; no specific file or documentation section is named in the issue. Add a brief mention of .git-blame-ignore-revs and why it is useful, then verify that the documentation builds or renders successfully.
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
- Needs clarification
- Newbie friendliness
- 35/100