ci: run the test workflow on pull requests against any base branch [RED-980] [ship] - #1489
Merged
Merged
Conversation
…ED-980] The test and check-ai-context workflows ran on pull_request only when the base branch was main or next/*, so a pull request stacked on a feature branch got no CI until it was retargeted. Both now run on every pull request, whatever its base, with the full suite: lint, both unit legs and all e2e jobs. Nothing is gated on the base branch; the e2e legs take one to three minutes each, in line with the unit legs, and the suite already tolerates concurrent runs across pull requests and shards. The push-to-main trigger, path filters and gate semantics are unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sorccu
force-pushed
the
simo/red-980-ci-trigger
branch
from
September 20, 2026 09:02
852f568 to
f4076a7
Compare
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.
The
testandcheck-ai-contextworkflows ran onpull_requestonly when the base branch wasmainornext/*, so a PR stacked on a feature branch got no CI at all until it was retargeted. Both workflows now run on every pull request, whatever its base, with the full suite: lint, both unit legs, and all e2e jobs.Nothing is gated on the base branch. The e2e legs take one to three minutes each, in line with the unit legs, and the suite already tolerates concurrent runs across PRs and Windows shards, so a stacked PR costs the same as one against
mainand gives the same signal. The push-to-maintrigger, the path filters, and the gate semantics are unchanged.Verified by parsing both files (a bare
pull_request:key means the default activity types) and by the CI run on this PR.🤖 Generated with Claude Code