Repository navigation
ci: aggregate required gates (stop branch-protection desync on renames/splits) #6519
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3e8e5d0
ci: aggregate required gates so renames/splits stop desyncing branch …
azooz2003-bit 7f32166
ci: rename the sharded job key tests -> app-host-unit-tests
azooz2003-bit 2286b9e
ci: track the tests->app-host-unit-tests rename in workflow guards
azooz2003-bit 9c882ec
Merge remote-tracking branch 'origin/main' into feat-ci-aggregate-gates
azooz2003-bit File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
ios-testsrequired-check will block PRs that never triggertest-ios.ymltest-ios.ymlhas apaths:trigger filter. For a PR that touches onlyweb/**, a server-side Go file, or any other path outside the listed patterns, the entire workflow never runs — meaningios-testsproduces no check status at all. GitHub reports the check as "Expected" (not "skipped"), and a required check that is absent blocks the merge.The PR description says "skip = pass here," but that only describes jobs that opt out inside a running workflow (e.g.,
ios-simulatorskipping becauseshould_run=false). It does not cover the case where the workflow itself never triggers. Ifios-testsis added to the ruleset's required list under the default "must be present and passing" mode, every web-only, Go-only, or other non-iOS-path PR will be permanently blocked.The safe configuration options are: (a) switch the GitHub Ruleset entry to "required if triggered" / allow-if-skipped mode, or (b) remove the
paths:filter from theon: pull_request:trigger so the workflow always runs and internal job conditions handle the skip logic (the same modelci.ymluses).