-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Multiple Triggers Are Not Working in Combination With Workflow Dispatch #32142
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
Comments
I created a pull request to allow parse |
That's great news! Thank you so much for the quick turnaround and helpful feedback! |
Just got gitea 1.22.3, above issue is still there.
|
I cannot reproduce it. Can you post your workflow file? |
This is the head of the file While pushing on branch Gitea Version
|
Short Description: If a pipeline contains the trigger “workflow_dispatch” and "push", the pipeline is not executed for push events.
Expected behavior: I would expect the pipline to be executed for both events. For a simple push as well as a manual execution.
Incorrect behavior: The pipeline does not react to push-trigger.
Current behavior: Only the manual execution works.
Reproduction: The following example contains two triggers. On the one hand the new “workflow_dispatch” as well as a simple "push". With this definition only the manual execution works. The pipeline is not executed during a push.
Workaround: Two independent workflows can be created as a workaround. The first deals with the “workflow_dispatch” and the second with the "push" event. The common logic is outsourced to a "workflow_call" and used by the previous workflows.
Gitea Version
1.23.0+dev-526-g3269b04d61
Can you reproduce the bug on the Gitea demo site?
No, because there are no runners available.
Log Gist
No response
Screenshots
No response
Git Version
2.30.2
Operating System
Debian 10.7
How are you running Gitea?
Gitea is running with two act_runners and an act_runner cache within Docker on a Debian system.
Database
SQLite
The text was updated successfully, but these errors were encountered: