semantic-release / semantic-release/commit-analyzer
Allow custom function in `releaseRules`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
There have been many JS tools that created some kind of static configuration DSL, and those DSLs always end up being janky to work with. Which is why so many tools have ended up allowing configuration to live in .js.
Since semantic-release already allows a .js config file, it's strange that releaseRules doesn't accept a custom function already.
But if it did it would be a better workaround for the lingering issues in #122.
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 locating how releaseRules is read and applied in the commit-analyzer codebase, then review the lingering issues referenced in #122. Define the supported custom-function behavior and verify that a JavaScript config can provide it while existing static releaseRules behavior remains intact.
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
- 35/100