semantic-release / semantic-release/commit-analyzer
Undo accidental commit messages.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
So if someone does a feat commit and then a BREAKING CHANGE commit, then there will be a major version.
However, what if someone makes a commit that says BREAKING CHANGE, but then realizes that it's actually not a breaking change. How can they nullify the accidental commit message and make it a minor change instead?
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 commit-analyzer interprets BREAKING CHANGE commits and the surrounding issue discussion to determine whether an override is intended. Define what behavior should turn an accidental breaking-change commit into a minor release, then identify the relevant tests needed to verify that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100