Install based on tags when available
Open
- Dominant language
- Go
- Stars
- 25
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Using the default branch is not desirable as we add more apps and make a better managed process.
This will make updates more sensible.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the installation and update flow, then trace how the default branch is selected and whether tags are available. Done means installations use an available tag instead of the default branch, with updates following the managed tag process.
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
- Needs clarification
- Newbie friendliness
- 25/100