on.<push|pull_request>.path ignores provided "path" and triggers for any PR.
See original GitHub issueon.<push|pull_request>.path
ignores provided “path” and triggers for any PR and any push.
Here’s the workflow, which doesn’t honor the “path” for PRs: https://github.com/ispc/ispc/blob/master/.github/workflows/rebuild-llvm10.yml
It does trigger workflow for any commit to master and any PR, ignoring providing path "llvm_patches/*10_0*"
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
How to trigger an action on push or pull request but not both?
I have a follow up question. Is it possible to run actions on branches which have not been pull requested, but don't run...
Read more >Triggers | Dev Cheatsheets
From On push pull request paths in the docs. Ignore a branch or tag. Note that if you use a rule from another...
Read more >update-webhook — AWS CLI 2.4.18 Command Reference
Works with pull request events only. FILE_PATH. A webhook triggers a build when the path of a changed file matches the regular expression...
Read more >Trigger pipeline only if certain files are changed
Concourse.ci, Drone.ci, and I assume other CI servers provide the option to restrict steps to commits only containing certain file paths.
Read more >Conditions
Same as pathsMatch (against commits for pull requests), except it will ignore deleted files in the supplied commits for the pull request. This...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @TingluoHuang! Was this ever fixed? I have similar behaviour with
on.<push|pull_request>.path-ignores
not ignoring markdown files specified like so:The
push
equivalent seems to be working flawlessly. Happy to create a new issue if need be.@hfaulds already created an internal issue to track that problem. 🎉