Skip to content

ci(upstream-sync): dispatch gate.yml so its checks satisfy the main ruleset - #41

Merged
AlexNegrescu26 merged 1 commit into
mainfrom
ci/dispatch-gate-for-sync
Oct 31, 2026
Merged

AlexNegrescu26 merged 1 commit into
mainfrom
ci/dispatch-gate-for-sync

Conversation

@AlexNegrescu26

Copy link
Copy Markdown
Collaborator

Summary

This PR prepares main for a ruleset that requires the gate, smoke and statechart checks before a merge.

upstream-sync currently calls gate.yml as a reusable workflow. A reusable call reports its checks as gate / gate, gate / smoke and gate / statechart. Those names never satisfy a required gate check. 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 gate job now dispatches gate.yml on the sync branch and watches that run with --exit-status. The dispatched run reports the plain check names on the sync commit. The merge job still needs gate, so a red gate leaves the PR open for a human. gate.yml drops workflow_call and its ref input, and gains workflow_dispatch. PORTING.md describes the new flow and the ruleset.

Verification

  • actionlint 1.7.12 on both workflows: no findings.
  • PR CI on this branch: see the checks below.
  • [INFERENCE] The full bot path waits for the next real upstream commit. GitHub documents workflow_dispatch as one of the events github.token may trigger. After this merges, a manual gh workflow run gate.yml --ref main shows whether the dispatched check names match.

@AlexNegrescu26
AlexNegrescu26 merged commit f18c6f9 into main Oct 31, 2026
3 checks passed
@AlexNegrescu26
AlexNegrescu26 deleted the ci/dispatch-gate-for-sync branch October 31, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant