-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Ensure PR workflows can run on all PRs (but still skip when they're not needed) #2237
base: main
Are you sure you want to change the base?
Conversation
4f7d3c1
to
2888f84
Compare
f40ac3c
to
b86d5e8
Compare
# In order to be able to have required checks, a workflow can't be entirely | ||
# skipped: see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks#handling-skipped-but-required-checks | ||
paths-filter: | ||
name: "Filter Paths" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's frustrating that GitHub actions works this way. With the objective of enabling auto-merge, I'm not sure there's another way around this, but I'm open to ideas if you have any?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'm not seeing a quick solution. Maybe the name could be the objective of the path filtering, something like "Conditional run" or "Run on path match"?
Closes #2279
This adds a
paths-filter
step to all workflows that run on PRs so that we can enable auto-merge, for more info about this read enabling auto-merge! In order to be able to have required checks, a workflow can't be entirely skipped: see Handling skipped but required checks.This also merges frontend CI workflows into one with multiple parallel steps, which should speed things up a bit. It also upgrades node versions to 20 and 22 across the board.