-
Notifications
You must be signed in to change notification settings - Fork 166
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
Not truly useable as a tool for developers of reusable actions #350
Comments
AFAIK actionlint is used to lint workflow files, not action files... |
Very likely, that's its current state, yes. But why not cover both? 😄 |
Because linting an Action is different than linting a workflow. The name of the tool is maybe a bit misleading, but its purpose is well defined on the homepage: "actionlint is a static checker for GitHub Actions workflow files." |
@AlexandreDecan it's not much different (did I ever say they were the same thing?), besides a few schema items. Anyway, this issue is a suggestion/feature request to the project. A project's purpose might change over time. :) |
Indeed :-) But remember you started your message with "I got a lot of false positives", my point was it's not surprising to have false positives if the tool is applied on the wrong file :-D |
This might be a duplicate of #46 ? |
I tried using
actionlint
in a small reusable Github Action that I develop and I got a lot of false positives (see below).All these missing sections and unexpected keys are completely fine when you are developing a reusable Github Action that gets published in the marketplace. For reference, I ran the tool over this file.
I would love if this tool had a toggle to tell it the action being linted is a reusable one and it could adapt accordingly to such scenario.
Thanks!
The text was updated successfully, but these errors were encountered: