-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False Positive On Aliases In Mapping Nodes #133
Comments
Yeah, aliases are actually not considered because I've never used them in my workflows and anyone didn't report that previously. But I agree this should not cause false positive at least. |
I created a minimal workflow to reproduce this: name: Test
on: push
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: Run my-action.
uses: my-organization/my-action@main
with: &my-action-inputs
a: b
c: d
e: f
- name: Run my-action again.
uses: my-organization/my-action@main
with: *my-action-inputs |
Consider also yaml anchors (if you didn't already)
|
I see a false positive on most aliases. This manifests as:
As it stands, if being used in superlinter, we cannot even use the command line to override this, since the exclusions aren't available in actionlint.yml. At this point we are left with:
All of which are sub-optimal. it suggests that the way this is linting is some AST that is running before aliases are resolved. |
This doesn't solve your problem, but to toot my own horn, MegaLinter runs significantly faster than Super-Linter, and has many more linters. It also has actionlint. |
Actionlint complains
"with" section is alias node but mapping node is expected [syntax-check]
on valid YAML syntax when anchors and aliases are used with mapping nodes:I am uncertain how one would suppress the error.
The text was updated successfully, but these errors were encountered: