Git tags for new versions are missing again
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
The latest release on RubyGems is 0.27.7, but the latest tag in this repository is 0.27.5. This is about the third time I’m reporting such issue, please automate this…
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
Review the repository's release and tagging process, then compare the RubyGems 0.27.7 release with the repository's latest 0.27.5 tag. Done means a documented or automated process keeps future releases and Git tags synchronized; the issue does not name a file, test, or entry point to start from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, ruby
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100