semantic-release / semantic-release/commit-analyzer
Why is this not using recommendedBumpOpts?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
See https://github.com/favoloso/conventional-changelog-emoji/issues/20#issuecomment-606773923
I wanted to use semantic-release together with the linked package, but unfortunately, it's not working out of the box, I rather need to define all the release rules within the release config, but conventional-changelog actually offers a recommededBumpOpts method that determines if a release is neccessary or not.
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 with the linked conventional-changelog discussion and compare its recommendedBumpOpts behavior with the commit-analyzer configuration used by semantic-release. Determine how release rules are currently supplied, then verify that the requested behavior works without manually defining every rule and that release necessity is evaluated correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100