mheap / mheap/pin-github-action
feature request: use longest tag available
- Dominant language
- JavaScript
- Stars
- 184
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
example, right now https://github.com/actions/checkout/tags shows the latest is v4.2.2. there's a v4.2.2 tag, but also they move the v4 tag to point to this release as the latest.
pin-github-action is putting v4 in the comment
` uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4`
when it would be more useful to put the fixed tag since later v4 will not correspond to that SHA.
` uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2`
I don't know how to do that in the general case, but it seems to me picking the "longest string" tag or "latest version number" would be an improvement.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named in the issue. Start by locating the tag-selection logic in pin-github-action and its existing tests, then trace how actions/checkout tags are resolved; the change is done when the comment uses the most specific stable tag for a pinned SHA and the existing test suite covers that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100