Skip to content
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

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

emma-sg
Copy link
Member

@emma-sg emma-sg commented Dec 13, 2024

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.

@emma-sg emma-sg added enhancement New feature or request tooling Tooling and developer experience work labels Dec 13, 2024
@emma-sg emma-sg self-assigned this Dec 13, 2024
@emma-sg emma-sg changed the title Combine frontend CI into one workflow Ensure PR workflows can run on all PRs (but still skip when they're not needed) Dec 13, 2024
@emma-sg emma-sg marked this pull request as draft January 7, 2025 17:35
@emma-sg emma-sg force-pushed the simplify-ci-runs branch 2 times, most recently from f40ac3c to b86d5e8 Compare January 7, 2025 20:10
@emma-sg emma-sg requested a review from SuaYoo January 7, 2025 21:13
@emma-sg emma-sg marked this pull request as ready for review January 7, 2025 21:28
@emma-sg emma-sg requested a review from ikreymer January 7, 2025 21:28
# 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"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only nitpick I have is that the checks now always show "Filter Paths":
Screenshot 2025-01-07 at 2 19 59 PM

Copy link
Member Author

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?

Copy link
Member

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"?

@SuaYoo SuaYoo self-requested a review January 9, 2025 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tooling Tooling and developer experience work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve CI parallelism & allow for auto-merge
3 participants