Conventional commits
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Should we enforce conventional commits for every squashed PR's commit message? Commits on a branch which are going to be squashed can look like preferred. But on the master branch it keeps history consistent and lets us auto generate release notes much better. Strict semver versioning probably doesn't matter much for an app like this, but I think it's in general a good convention
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 how pull requests are squashed and how releases or release notes are generated in this repository. Define whether conventional commits should be enforced and determine what checks or workflow changes would make squashed commits comply, then verify the resulting history and release-note generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100