Ignoring Bots in The Commit History
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 33
- Forks
- 104
- Avg merge
- 12h 3m
- Merged PRs (30d)
- 10
Description
Some quick advice on how to ignore the various GitHub Action bots
in the commit history. This helps keep the commit history clean and
focused on the work done by human contributors, and lowers the risk of
merge conflicts when people try to contribute upstream (ie me)
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 repository's GitHub Actions configuration and recent commit history to identify which bots are involved. Clarify whether the desired outcome is contributor guidance or a repository change, then document or implement a way to keep bot commits out of the human-focused history and verify it with a representative workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, developer-experience
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100