canonical / canonical/concierge
Support releasing from the 1.5-maintenance branch
Open
Nobody has claimed this yet.
rainy day
- Dominant language
- Go
- Stars
- 17
- Forks
- 11
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 6
Description
Currently this goes to latest/stable, *replacing* newer releases 😞.
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 configuration or command that currently sends releases to latest/stable, then trace how the source branch is selected. Update the release flow so a release from 1.5-maintenance targets the corresponding maintenance channel without replacing newer releases, and verify both branch paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100