nebula-plugins / nebula-plugins/nebula-release-plugin
version inference strategy based on commit messages
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Does Nebula work with a version inference strategy based on commit messages (Conventional Commits )? For instance, if the commits made after the last version tag begin with "BREAKING CHANGE:", does it increment the major version, If not, does it evaluate if the commit message starts with "feat" to increment the minor version, If not, does it evaluate if the commit message starts with "fix" to increment the patch version, Otherwise, does not it increment nothing
Contributor guide
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
No file or test is named in the issue. Start by locating the release-version inference entry point and the code that reads commits after the last version tag, then check whether Conventional Commits are already supported; done means the requested BREAKING CHANGE, feat, fix, and no-op rules are defined and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100