Commit message convention
Open
Nobody has claimed this yet.
enhancement
help wanted
question
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
Can we follow https://chris.beams.io/posts/git-commit/ to unify the commit message style?
It'll be good to follow a styling guide, just like coding style.
cc @nodejs/docker
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
Read the linked Chris Beams commit-message guide and inspect this repository’s contributor documentation for any existing commit conventions. Identify where a project-wide convention should be recorded; done means the chosen guidance is documented consistently for contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100