mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2476] workflow is not valid / Unknown property inputs #1141
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1141
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BBBmau on GitHub (Sep 29, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2476
Bug report info
Command used with act
Describe issue
This happens on a fresh install of act using
brew install actLink to GitHub repository
https://github.com/commaai/openpilot
Workflow content
Relevant log output
Additional information
No response
@sebastien-perpignane commented on GitHub (Oct 11, 2024):
Hi,
I think that's because
actexpects workflow yaml files in .github/workflows/ directory, not action yaml files.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 :)
@ChristopherHX commented on GitHub (Oct 13, 2024):
...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
@sebastien-perpignane commented on GitHub (Oct 14, 2024):
Hi @ChristopherHX
Do you think that some code change ignoring yaml files named "action" in .github/workflows would be a correct fix ?
@ChristopherHX commented on GitHub (Oct 14, 2024):
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
@tsny-houzz commented on GitHub (Oct 14, 2024):
This is also happening to me and only with
compositeworkflows.@ChristopherHX commented on GitHub (Oct 15, 2024):
I don't like this term, because it is not 100% clear if it is a workflow or an action.
-Wcli parameter to a actual workflowIMO 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
@github-actions[bot] commented on GitHub (Apr 14, 2025):
Issue is stale and will be closed in 14 days unless there is new activity