We use github actions pretty extensively, and have a lot of workflows defined. Occasionally it seems that actions are triggered regardless of the filtering rules defined in the workflow.
For example, with the following
on clause the workflow at
on: push: paths: - 'docs/**'
Was triggered even though in the branch only the following files are changed:
In the same instance, a bunch of other workflows were triggered when they should not have. More examples of
on: push: paths: - '**.md' --- on: push: paths: - '**.go' - 'go.mod' - 'go.sum' --- on: push: paths: - '**.pb.go' - '**.proto'
I think that all of our workflows that have
paths filters were triggered. Maybe I don’t quite understand the logic causing the trigger.
Could rebasing the branch have anything to do with it?