-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
workflow is not valid / Unknown property inputs #2476
Comments
Hi, I think that's because As the log says, "DEBU[0000] Reading workflow '/Users/mau/Dev/openpilot/.github/workflows/auto-cache/action.yaml' " I think you should consider to move your actions in a .github/actions dir to make your repo compatible with GitHub and with act. That's what I would try to do if I had the same issue :) |
...The problem is actually that a feature request for GitHub Actions ",Workflows in subdirectories of .github/workflows" has been implemented in act A PR that reverts/removes the feature would resolve this Older versions would have handled an action.yml file as an empty workflow, which is incorrect |
Do you think that some code change ignoring yaml files named "action" in .github/workflows would be a correct fix ? |
No, action.yml is a valid name for a workflow in .github/workflows until you can provide me an example on GitHub that shows the opposite. Ignoring files without .yml/.yaml extension should be implemented in my opinion |
This is also happening to me and only with |
I don't like this term, because it is not 100% clear if it is a workflow or an action.
IMO putting yaml files that are not workflows in .github/workflows is going to be a problem for you soon, when GitHub adds support for organizing workflows in folders this feature got label backlog for GitHub Actions |
Bug report info
Command used with act
Describe issue
This happens on a fresh install of act using
brew install act
Link to GitHub repository
https://github.com/commaai/openpilot
Workflow content
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: