Tag releases please
Open
- Dominant language
- C
- Stars
- 2.5k
- Forks
- 239
- PR merge metrics
- No merged PRs in 30d
Description
Could you please tag the commit used to build each [package published to PackageCloud](https://packagecloud.io/github/glb-director)?
It's tricky to uncover which version of the source corresponds to, e.g., v1.0.5, v1.0.7, etc.
I wouldn't expect everything to be tagged retrospectively but at least for future releases, and ideally the most recently published package.
Contributor guide
Research direction
Start by tracing how releases are built and published to PackageCloud, then compare the most recently published package with the repository's commit history. Done means the latest package can be matched to a tagged commit and future package releases receive corresponding tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100