Recommend commit guidelines?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 148
- Forks
- 41
- Avg merge
- 1m
- Merged PRs (30d)
- 7
Description
There is some value already in converging in the format of commit messages alone.
But also, by doing that, we could at some point adopt tools that process and digest the commit history of a project to produce automated changelogs and/or decide the next semantic version to be published (eg, semantic-release).
Contributor guide
No contributing guide indexed for this repository
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 linked Angular DEVELOPERS.md Git commit guidelines and the semantic-release project referenced in the issue. Determine whether this repository has an existing contributor or release-guidelines document to update; done means the desired commit format and any changelog or semantic-versioning expectations are explicitly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100