semantic-release / semantic-release/commit-analyzer
Use the standard `conventional-changelog-preset-loader` to load presets
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
I think using conventional-changelog-preset-loader should be the best solution for #589 and reduce the burden on the @semantic-release/commit-analyzer maintainer.
Import loadPreset function from the package and use it to load the preset:
import { loadPreset } from 'conventional-changelog-preset-loader'
loadPreset('angular').then((config) => {
// do something with config object
})
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 the existing preset-loading entry point in the commit-analyzer code and review issue #589 for the behavior being addressed. Compare that path with the documented conventional-changelog-preset-loader API. Done means presets are loaded through loadPreset and the existing analyzer behavior remains covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100