ci: adopt auto-merge, so a green PR here merges without waiting for a person - #22
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.
Adds a thin caller of
_auto-merge.ymlinbounded-systems/.github.What it does. On every non-draft PR from this repository, asks GitHub to merge it the moment its required checks pass — under an App identity minted through the org's OIDC broker, never this workflow's own token. A PR that is already clean merges at once.
What it does not do. It merges nothing the branch rules would refuse.
standard / testandpr-claim / pr-claimare required on the default branch here, so a red or unclaimed PR is armed and never merges. The rules are the gate; this file only removes the wait for a person after they pass.Why an App identity. A merge made under a workflow's
GITHUB_TOKENstarts no workflow runs on the default branch; an App-attributed merge does, so the repo'spushlanes keep firing after an automated merge. The door (pr-arm) is pinned to the exact commit this caller pins, so neither can move without the other.No checkout, never
pull_request_target. The PR's code is never fetched or executed. A fork PR carries no OIDC identity and is skipped.Claim-issue: bounded-systems/.github#388