Skip to content

ci: adopt pr-claim, so PRs here are checked against a live Front Desk claim #341

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.

Sign up for GitHub

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
claude merged 1 commit into from
Sep 1, 2026
Merged

ci: adopt pr-claim, so PRs here are checked against a live Front Desk claim #341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 16 additions & 10 deletions .github/workflows/pr-claim.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,17 +26,23 @@ name: pr-claim
# reports as `unreadable` and counts as NOT claimed, the fail-closed direction,
# but a false red rather than a true one.
#
# WHY THE PIN IS bc4cb7d. That is #299, the newest commit to touch
# WHY THE PIN IS bc4cb7d. That is `.github`#299, the newest commit to touch
# `_pr-claim.yml`: it fails a PR whose BODY says keep an issue open and whose
# COMMIT says close it. A squash merge honours the commit, which is how #296
# closed the very issue it promised to leave open and made the follow-up PR
# naming it unmergeable (`.github-private`#780, #781).
# COMMIT says close it. That check exists because #296 carried
# `Claim-issue: …#295` and `Closes #295` at once, went green, and closed the
# issue on squash anyway -- which made the follow-up PR naming it unmergeable
# (`.github-private`#780, #781). A squash merge honours the commit message, so
# nothing before bc4cb7d can catch it.
#
# It supersedes 8a56f22 (#283). THIS REPO WAS ONE OF THE SIX still on that older
# door while 37 of 43 deployed callers had moved past it (#322) -- so the repo
# that owns `_pr-claim.yml` was checking its own PRs with a version of it that
# predates #299. The roll script does not own this file, so it had to be bumped
# by hand alongside the template and its GUARD.
# It supersedes 8a56f22 (#283, which named which state each candidate issue is
# in). That pin was carried here while 37 of 43 deployed callers had already
# moved PAST it -- Dependabot bumps each repo's pin independently -- so the
# template was rolling a door older than most of the fleet was running, and
# `.github`'s own caller was among the six still on it (#322).
#
# The roll script refuses any template not pinned here, so this constant and
# its GUARD must move together or the roll hard-fails. That is the guard
# working, not an obstacle to route around.
#
# IT DOES NOT AUTHENTICATE THE CLAIMANT. A green `pr-claim` means "an open,
# claimed issue was named", and no more — an author can name any claimed issue,
Expand Down Expand Up @@ -75,4 +81,4 @@ jobs:
issues: read
pull-requests: read
# SHA-pinned, per org policy — never a branch.
uses: bounded-systems/.github/.github/workflows/_pr-claim.yml@bc4cb7dada47cc59eed416372a4851201bd6f503
uses: bounded-systems/.github/.github/workflows/_pr-claim.yml@bc4cb7dada47cc59eed416372a4851201bd6f503
Loading