Run CI on every pull request, not only those targeting main - #35
Merged
Merged
Conversation
prkrtg
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
branches: [main]filter from both workflows'pull_requesttrigger. That filter matches the base branch, so a PR stacked on another feature branch got no checks at all, which is exactly when they are most wanted. Found while stacking the keygrabber work: Add the keygrabber control keywords and a testable scheduler #34 reported "no checks reported" purely because its base was a feature branchpathsfilters and the push-only-on-main trigger, so this widens which PRs are checked without widening what triggers a buildpagesconcurrency group from the workflow onto thedeployjob. It exists to stop two publishes overlapping, but at workflow scope it also serialized every PR's docs build behind every other one, which matters more now that more PRs build. Deploys still run one at a time and are still never cancelled mid-publish