Action with on: push: [main] and paths config is not triggered when PR is squash and merged

[fetilla]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

I have configured a github action with the following event:

on:
  push:
    branches:
      - main
    paths:
      - 'schemas/**'

I was expecting to see the workflow triggered after a PR is merge to main and it contains some modification of a file inside schemas folder. The issue is depending on how the PR is merged the behaviour is differnt:

• Rebase and merge: The workflow is triggered, no issues.
• Squash and merge: The workflow is not triggered.

I found issues related like this one https://github.com/orgs/community/discussions/25812#discussioncomment-4041758, which was closed but it contains comments describing a similar behaviour.

[jonattasmoraes]

This behavior is expected due to how squash merges are created.
With rebase and merge, GitHub generates real commits on main, so the paths filter works correctly.
With squash and merge, GitHub creates a single new commit and the file-level change metadata isn’t always preserved in a way that triggers paths filters on push.

This is a known limitation and has been discussed before.

If you need consistent behavior, consider triggering on pull_request with paths, and checking github.event.pull_request.merged == true, or avoid squash merges for workflows that depend on file path filters.

[andriiafanasiev]

This is expected behavior due to how GitHub handles path filters on squash merges. When a PR is squashed, the resulting commit is a single new commit that may not match the original path changes individually, so workflows with paths: may not trigger. Currently, there’s no workaround to make paths: fire reliably on squash merges — the workflow will always reliably trigger on Rebase and merge or direct commits.

[Ryangr0]

I spent over an entire's day worth of time chasing ghosts. If you arrive here, please be sure you don't have [skip ci] in your commits...

[mycodeself]

@Ryangr0 so you were able to make it work with squash and merge and paths? or are you just using different strategy?

[fetilla]

@Ryangr0 you are absolutly right, during PR we were comitting with [skip actions] and when you squash it for any magic reason gh actions detects that commit is part of the squash and was not being executed on main. WIth rebase it was not working neither...

At the end we implemented our own version of skip 😆 .