Misleading guidance on workflow filters

[DavidSlayback]

trafficstars

Code of Conduct

• [X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

Using Filters

What part(s) of the article would you like to see updated?

I didn't submit this as a PR because I don't know if the mistake is in Docs or in GitHub Actions.

In the docs, it states:

If you define both branches/branches-ignore and paths/paths-ignore, the workflow will only run when both filters are satisfied.

However, this is not true. Both in my own experience writing Actions for my company and in StackOverflow threads, it's clear that GitHub uses a logical OR instead of the implied AND from above. E.g., if I specify in a workflow:

on: 
  push:
    branches:
      - main
    paths:
      - "src/**"

I expect that the above should only trigger on a push to the main branch that alters files under src. However, it actually triggers on BOTH any push to main and any push to another branch that changes src files.

If this is the desired behavior, then the docs should be changed to reflect it. If it's not the desired behavior, then Actions should be changed to reflect the docs

Additional information

No response

[welcome[bot]]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[nguyenalex836]

@DavidSlayback Thank you for opening this issue! I'll get this triaged for review ✨

[DavidSlayback]

Any updates on this? We wound up using a 3rd-party Github Action, but it'd be much cleaner to incorporate into the on trigger

[github-actions[bot]]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert :eyes:

[nguyenalex836]

@DavidSlayback Hello! 👋 Thank you for your patience while our engineering team reviewed!

They are asking if you are able to replicate this in a public environment. Having an example they can look at, rather than needing to fabricate that repository structure and any user initiated changes would help them investigate further 💛

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful.