nebula-plugins / nebula-plugins/nebula-release-plugin
Improve releasing from an existing tag
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Run through more test cases to discover edge cases.
including but not limited to:
- Releasing from a tag that is not at head
- Checking that the commit the build is releasing from is at the last tag
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 locating the release flow for releasing from an existing tag and run it against the two cases named in the issue: a tag that is not at head and a build commit that is not at the last tag. Inspect how the current release path validates these conditions. Done means the relevant edge cases are covered and the expected behavior is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100