Workflow only executing on force push

I have this workflow set up to execute on push. The weird thing is that it doesn’t execute when I push to the dev branch but whenever I force push it does! Why is that?

Hi @husamibrahim , thanks for the repo. I can see the workflow has run on lots of commits on the dev branch. Please could you identify the commits at the head of the pushes you felt should have run but didn’t? Thanks!

Thanks @timruffles for taking the time to look into this. Here are a couple of commits which should have triggered the workflow but didn’t …

I didn’t bother force pushing in these two cases because these were minor commits, but they should have triggered the workflow according to the defined rules. Some of the other commits that did trigger the workflow such as this one (26b72ada308da7667119bbb97fa6973d57335ca5) I pushed first and when the workflow didn’t run I kind of cheated by changing the commit hash at the head (git commit --amend --allow-empty) and then force pushing to get the workflow to run.

@husamibrahim yes, having a look that did indeed get incorrectly filtered out!

We’ve shipped a big update to how filters work, so you shouldn’t see the same issue recur. If you do, please let me know :bowing_man:‍♂

1 Like