Repository navigation
ci(upstream-sync): dispatch gate.yml so its checks satisfy the main ruleset - #41
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
This PR prepares
mainfor a ruleset that requires thegate,smokeandstatechartchecks before a merge.upstream-synccurrently callsgate.ymlas a reusable workflow. A reusable call reports its checks asgate / gate,gate / smokeandgate / statechart. Those names never satisfy a requiredgatecheck. A personal repository also cannot exempt the GitHub Actions bot from a ruleset. Together, that would block every bot sync merge once the ruleset is on.The sync's
gatejob now dispatchesgate.ymlon the sync branch and watches that run with--exit-status. The dispatched run reports the plain check names on the sync commit. Themergejob still needsgate, so a red gate leaves the PR open for a human.gate.ymldropsworkflow_calland itsrefinput, and gainsworkflow_dispatch. PORTING.md describes the new flow and the ruleset.Verification
actionlint1.7.12 on both workflows: no findings.workflow_dispatchas one of the eventsgithub.tokenmay trigger. After this merges, a manualgh workflow run gate.yml --ref mainshows whether the dispatched check names match.