Consider tagging git?
Open
- Dominant language
- Go
- Stars
- 216
- Forks
- 31
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Hi! I help the Debian Go team and we package this project (for `pwru`) however it is hard to know which commits are considered stable. Would you consider making tags to make it more easy for us to pick the "right" version to package? Thanks.
Contributor guide
Research direction
No files or tests are named. Review the repository history and current Git tag state first, then compare the Debian Go team's packaging needs with a proposed stable-version convention. Done means the project has an agreed tagging scheme and tags that let packagers select the right pwru version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100