Why does a merge commit not trigger an on: push workflow?

[uladkasach]

I’ve setup a workflow that runs on: push - with no conditions.

after merging a PR with the squash and merge option, the resultant commit on the master branch did not trigger the workflow!

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 on: push and when merging?

[kubkon]

AFAIK if you configured your workflow with something similar to

on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

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…

[jacky0wl]

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

[cormacrelf]

https://ghp.lvmhsh.cnmunity/t5/GitHub-Actions/Github-push-actions-suddenly-not-triggering/m-p/36988#M2753

[Yanjingzhu]

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?

[totoprayogo1916]

Doesn't work if pushed by bot, like github-actions.

[artemgavrilov]

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 main branch at all. There are no errors or anything else, CI workflows just not started at all.

[ekampf]

@artemgavrilov where you able to solve?

[artemgavrilov]

Hi @ekampf , this problem occurs because of this restriction. So solution is to not use GITHUB_TOKEN for enabling auto-merge option.

[uladkasach]

all working as expected now. thank you!

[intolerance]

Having issues with actions triggering on merge currently. Are you guys sure it wasn’t just temp. fixed?

[ngmiduc]

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)

name: Staging Deployment

on:
  workflow_dispatch:
  push:
    paths:
      - ...
    branches:
      - dev

prod: (when merging the release branch to master, this workflow is not triggered)

name: Prod Deployment

on:
  workflow_dispatch:
  push:
    paths:
      -  ...
    branches:
      - master

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

[Stig-Johnny]

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.

[omri-shilton]

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.

[polo4096]

same here when working with merge commits and paths filtering, any update ?

[alefranz]

Bumped into this issue after refactoring workflows to trigger another workflow in same repo.
It seems that having secrets: inherit is enough to stop triggering the workflow on push.

Is there any known workaround?

This limitation combined with cli/cli#8145 it means when you need to break glass you are forced to bypass the merge queue, but given the push event is not triggered, you have no way to run a workflow after merge :|