Remove actionlint self-repository syntax workaround after upstream support ships
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Check whether a released actionlint version supports $/ self-repository references, then inspect the pinned rhysd/actionlint action and .github/actionlint.yaml. Update the pin and remove the corresponding suppression, deleting the file if empty. Run actionlint, zizmor, and the full CI suite to confirm they pass without the workaround.
Written by the indexing model from the issue text.
Description
Context
PR #210 adopts GitHub's $/.github/... self-repository syntax for reusable workflow calls. This syntax resolves workflow references from the exact commit being run.
Actionlint v1.7.12 does not yet recognize $/.github/..., so .github/actionlint.yaml narrowly suppresses its workflow-call false positive for these references. Zizmor remains fully enabled.
Upstream tracking:
- actionlint issue: https://github.com/rhysd/actionlint/issues/711
- actionlint implementation PR: https://github.com/rhysd/actionlint/pull/732
Done when
- A released actionlint version supports
$/self-repository references. - The pinned
rhysd/actionlintaction is updated to that release. - The corresponding suppression is removed from
.github/actionlint.yaml(and the file is removed if empty). - Actionlint, zizmor, and the full CI suite pass without the suppression.
- Dominant language
- Go
- Stars
- 242
- Forks
- 28
- Avg merge
- 12h 49m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
Similar issues
-
accepted bug wg/router-models-inference-runtime
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/semantic-router#4524 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-sdk-go-v2#3576 ·
Maintainers usually reply within 1 day
-
enhancement needs-verification phase-2-optimize
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FootprintAI/Containarium#2277 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
keyxmakerx/Chronicle#1061 ·
Maintainers usually reply within 1 day