Make `prepare-release` more transactional
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 18
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If a step fails, it should be as side-effect free as possible. For an example right now it can leave the prepare-release-xxx branches behind, which in turn makes a re-run fail.
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 at the prepare-release entry point and reproduce a failed step to observe which prepare-release-xxx branches remain. Done means failed runs leave as few side effects as possible, including no leftover branches that cause a rerun to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100