GitHub Community
On: workflow_run: does not work for me #25288
-
|
Hi all,
and a workflow that should be triggered after the CreateRelease workflow runned
second workflow is never triggered, why? thanks! I want to create a release in a workflow triggered by a tag push, how can I do it? |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 2 replies
-
|
Is the workflow “GitHub Linux Release” existing on the master or default branch? Here is a recent reported similar topic as reference: @andrewconnell, There are few points maybe can explain the problems: In addition, if you want the workflow “GitHub Linux Release” is triggered after the workflow “CreateRelease” completed, you should only use the type “completed”. If the problem still exists, please share your repository with us (if possible), so that we can check more detailed configurations related to the workflows to analyze the root cause. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the answer, at the end I solved using a multi job workflow. but I understood your suggestion, thanks for the help. love GitHub and its community. |
Beta Was this translation helpful? Give feedback.
-
|
@sblantipodi : please let me know how did you solved this and what changes you have done w.r.t the example which you have given |
Beta Was this translation helpful? Give feedback.
-
|
I encountered the issue on my repo here. So the workflows exist on the master but the default branch cant be the master because we depend on another functionality(wei/pull) to pull from the project that is forked. Any suggestions as to why this would happen or how I could remedy it ? |
Beta Was this translation helpful? Give feedback.
-
|
The workflow dispatch UI on the website has a drop-down menu to select a branch. Maybe put some placeholder workflow on the default branch and the real workflow on the desired branch (here: master), with the exact name file name? |
Beta Was this translation helpful? Give feedback.
-
|
Ok so I am managing everything on the default branch now as actions on master don’t work like they should. Now the issue I am having is all the Windows actions get run but as soon as the last windows one is done(WindowsLibd3d12) the one that depends on that one(html5 library) doesn’t get called. Could it be related to the fact that they use a different platform(one windows and the other ubuntu) or is it because libd3d12 is the last file and html5 library is the first file in the folder hierarchy ? |
Beta Was this translation helpful? Give feedback.
-
|
So after doing a Test it seems to be that workflow_run is capped at max 3 subsequent runs ? that is weird |
Beta Was this translation helpful? Give feedback.
-
|
It could be a deliberate limit to prevent endless loops of workflows being triggered, but if this is actually a restriction then it should be documented. |
Beta Was this translation helpful? Give feedback.
-
|
Have also just hit this undocumented arbitrary limit of 3 consecutive runs using on workflow_run. |
Beta Was this translation helpful? Give feedback.
-
|
Met The same problem and find its in the following document: Events that trigger workflows - GitHub Docs: Note: This event will only trigger a workflow run if the workflow file is on the default branch. |
Beta Was this translation helpful? Give feedback.
-
|
does this mean the workflow will only run on the default branch? |
Beta Was this translation helpful? Give feedback.
-
|
I am also seeing this issue, was there a resolution to it? My workflow files are all on the master (default) branch and I am not seeing my test workflow run after the initial build workflow completes. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use workflow_run: trigger from a workflow in different repository? I think this is more of a 'real use case' scenario. |
Beta Was this translation helpful? Give feedback.
@sblantipodi,
Is the workflow “GitHub Linux Release” existing on the master or default branch?
To trigger a workflow runs on the workflow_run event, the workflow file should exist on the master or default branch.
Here is a recent reported similar topic as reference: