mas-cli / mas-cli/homebrew-tap
Create retroactive version tags & GitHub Releases
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 5
- Avg merge
- 25m
- Merged PRs (30d)
- 2
Description
Create retroactive version tags & GitHub Releases.
Use backdated signed annotated tags, if the release process can be switched from lightweight to signed tags.
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
Start by reviewing the repository's existing release process and GitHub tags and Releases. Determine whether retroactive signed annotated tags are feasible instead of lightweight tags, then create the historical version tags and corresponding GitHub Releases. Done means the requested versions are represented accurately and the release process decision is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100