Repository navigation
chore: add a stable CI merge gate - #807
Merged
Merged
Conversation
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.
Summary
Add a stable
CI Gateover frontend checks, backend checks, and desktop E2E. It runs after unsuccessful prerequisites and passes only when every prerequisite succeeds, so failed, cancelled, and unexpected skipped jobs cannot produce a successful gate. Document how to maintain its dependencies and migrate branch protection.Related Issue
Not applicable.
Verification
A local harness executed the gate script extracted from the workflow across prerequisite result combinations, invalid input, and an additional future dependency. It also confirmed that the existing jobs and workflow settings are unchanged. Actionlint and targeted Oxfmt validation passed, along with the pre-push TypeScript and Oxlint checks.
Not verified locally: frontend and backend application suites or desktop E2E; the pull request runs these in CI.
Notes
Keep the three existing required checks until this pull request passes CI and is merged. Then replace them with
CI Gatefrom GitHub Actions, preserving the other branch-protection settings.