nebula-plugins / nebula-plugins/nebula-release-plugin
Support for overriding branch name for CI
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Many CI systems checkout repositories in a detached HEAD state, which makes it quite difficult to determine the source branch. These systems generally provide a variable containing the source branch name though. Can we add a parameter to override the default branch resolution? Judging by the code this would be pretty trivially added to SemVerStrategy. Perhaps a new parameter named "release.branch" or "release.branchOverride" could be used in place of grgit.current.name if detected. I can supply a PR if this change is acceptable.
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
Start by reading SemVerStrategy and the branch-resolution use of grgit.current.name. Trace how release parameters are exposed, then verify that a configured branch override is used for detached CI checkouts while the existing branch lookup remains the default when no override is supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100