Shell Releases missing after automation-core
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 14
- Forks
- 52
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 27
Description
https://github.com/rancher/shell/releases
vs
https://github.com/rancher/shell/tags
We should still use releases (and drafts of them) as they help create changelogs/diffs between versions. They are IMO also critical to greater workflows that should rely on looking up published (non-draft) Releases to know what the latest release of a branch is. As relying on Tags alone may not accurately reflect if release assets are complete.
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
Compare the repository's Releases and Tags pages, then trace the automation-core release entry point mentioned in the issue. The change is complete when releases, including drafts, are created and remain usable for changelogs, version diffs, and identifying the latest published branch release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100