-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
GH Actions: fix order of path filters for push and pull-request events #12686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 0e7303b.
Test Results - Preflight, Unit21β579 testsβ Β±0βββ19β927 β
Β±0βββ6m 19s β±οΈ +5s Results for commit 6a37fea.βΒ± Comparison against base commit 79b46be. |
This seems like a very strange fix for this error. Could you explain more how the old evaluation logic worked, and how this change fixes it? |
Test Results - Alternative Providers597 testsβββ420 β
ββ14m 56s β±οΈ Results for commit 6a37fea. |
@simonrw Yes, indeed. The problem is that order of path patterns matter and it was applied in the incorrect order. Now, we firstly exclude all files in the |
Test Results (amd64) - Integration, Bootstrapββββ5 filesββββββ5 suitesβββ2h 22m 19s β±οΈ Results for commit 6a37fea. |
Motivation
Thanks to this PR, it was discovered that the order of path filters for push and pull_request triggers was incorrect. As a result, the
aws-main.yml
workflow was not triggered whenaws-tests.yml
was updated in the PR.Changes
.github
files except files in theactions
folder,aws_main.yml
, andaws_tests.yml