GitHub Community
Why does a merge commit not trigger an on: push workflow?
#25812
-
|
I’ve setup a workflow that runs after merging a PR with the I had expected that adding a commit to the master branch would be considered a “push”, regardless of “who” pushed it (in this case, the push comming from the github ui). Is this the expected behavior? If not, how could i trigger that workflow on both |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 5 replies
-
|
AFAIK if you configured your workflow with something similar to it should trigger on a merge commit treating it as “on: push”. Lately, and by that I mean since approx yesterday, there is something amiss, as this also doesn’t work for me now in this repo, and it used to work just fine in the past. Perhaps this is related to this issue? Both seem to coincide in time… |
Beta Was this translation helpful? Give feedback.
-
|
I have a workflow that is triggered just the way yours is but the workflow triggers when the pull request is opened, not when merged to main, I have no Idea why |
Beta Was this translation helpful? Give feedback.
-
|
When a merge commit push to master, it will trigger the workflow with on:push. There is the incident which caused your issue. https://www.githubstatus.com/incidents/42hkbtl63nmn. We have resolved it. Can you check whether it works fine in your side now? |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't work if pushed by bot, like github-actions. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like we faced same issue. We've setup Enable auto-merge on a pull request and then we discovered that such merges don't trigger CI on |
Beta Was this translation helpful? Give feedback.
-
|
@artemgavrilov where you able to solve? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ekampf , this problem occurs because of this restriction. So solution is to not use |
Beta Was this translation helpful? Give feedback.
-
|
all working as expected now. thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Having issues with actions triggering on merge currently. Are you guys sure it wasn’t just temp. fixed? |
Beta Was this translation helpful? Give feedback.
-
|
I have also issues when merging to master, that results in no trigger of the workflow. The weird thing is, that it works for staging but not for prod. staging: (when merging to the dev branch, this workflow is triggered) prod: (when merging the release branch to master, this workflow is not triggered) I don't get it somehow, the workflows are quite identical. We have a mono-repo setup where we use github actions to deploy some of our services, where master is our prod branch and dev is our staging branch |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem when using paths and merge commit. There are files changed in the paths. But action does not trigger. If I change something and then do an append push it works. |
Beta Was this translation helpful? Give feedback.
-
|
We are also experiencing this issue. we have dev and main branch. and when doing a merge from dev to main and then pushing, on: push doesnt not trigger the workflow. |
Beta Was this translation helpful? Give feedback.
When a merge commit push to master, it will trigger the workflow with on:push.
There is the incident which caused your issue. https://www.githubstatus.com/incidents/42hkbtl63nmn. We have resolved it. Can you check whether it works fine in your side now?