Release automation should close release issues when the steps are complete
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
The release-go build is the last step for each version-specific release, and the release-go-images build is the final step for the day's overall release. If these builds succeed, it's expected that no more steps are necessary for their associated tracking issue. Closing them is a good indication to the dev running the release that a step is done. If the dev notices something didn't go right (even though automation thinks it went fine), they can reopen the issues.
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 release-go and release-go-images builds and the tracking issues they correspond to. Review how successful build completion is recorded, then verify that each associated issue closes only when its final build succeeds and can still be reopened when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100