Repository navigation
ci: add pull request status labels, a backlog skill and a typescript release script - #1919
Merged
Merged
Conversation
A workflow gives every open pull request exactly one Status: label, recomputed from what GitHub reports: draft, needs rebase, CI failing, waiting on author, waiting on review or ready to merge. Only reviews from accounts with write access approve or block, and a check is read from its newest run, so a failure that passed on a re-run does not read as CI failing. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
release.cjs becomes .github/scripts/release.ts, and the configure job runs scripts/plan-release.ts with node, the way pr-body.yaml and pr-status.yaml run their scripts. The plan and its outputs are unchanged. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
Every open pull request now carries one
Status:label saying whose turn it is, a new user-invoked skill works the issue backlog in small batches that read those labels, and the Release workflow plans its run from a TypeScript script like the other workflow scripts.Changes
PR Statusworkflow gives each open pull request exactly one ofStatus: Draft,Needs Rebase,CI Failing,Waiting on Author,Waiting on RevieworReady to Merge. A draft outranks a conflict, a conflict outranks a failed check, and a failed check outranks the review state. It runs when CI, Commitlint or PR Body completes, every 15 minutes, and on dispatch; it gates nothing. On merge it starts labelling every open pull request.Waiting on Reviewwhen its author pushes after the feedback or requests the review again. The author's own replies, bot reviews, and approvals or change requests from accounts without write access do not count, and an approval counts only for the head commit.working-the-backlogskill, which only a user can invoke, turns one batch of backlog issues into pull requests. It first clears the operator's pull requests labelledCI Failing,Needs RebaseorWaiting on Author, then picksDifficulty: Lowissues andDifficulty: Mediumbugs that share no file with any open pull request, waits for the operator's go-ahead, and stops at five open pull requests.configurejob plans the run withnode scripts/plan-release.tsinstead ofactions/github-script. The plan, its five outputs and the notice for a superseded major are unchanged.tsctype-checks every file under.github/scripts/, so a new script there needs notsconfig.jsonedit, and knip no longer treats.github/scripts/*.cjsas entry files or ignores agithub-scriptdependency.Decisions
mainruleset identifies its required checks. Two workflows with a job of the same name would be read as one check.Status:label instead of working out conflicts, failed checks and open feedback itself, so the two cannot disagree. The cost is that a plain conversation comment, which the labels ignore, does not send the skill back to a pull request.scripts/plan-release.tstakes the version by importing the rootpackage.json, which types it at compile time, where the old script read and parsed the file at run time. The reading of the ref, the tags and the version now sits in that entrypoint, outside the coverage gate likescripts/check-pr-body.ts, so the two tests that asserted those reads are gone.Risks
mainafterwards is its first real run. If it fails,configurefails and nothing is built or published until it is fixed.Waiting on Author; the skill treats one where its reply is the last word as cleared.Waiting on Authorafter its author has pushed.Notes
For this repository's current version and tags,
node scripts/plan-release.tswrote the same five outputs as the oldrelease.cjsrun through a stand-in foractions/github-script; on a ref that is not a release ref it exited 1 and wrote nothing. The status query, run read-only against this repository, was accepted by GitHub and planned one label for each of the 13 open pull requests.Adversarial review
Reviewed at commit bc341ed. pnpm check: green.
Findings
Status: Ready to Mergeor hold it atStatus: Waiting on Author— querylatestOpinionatedReviewswithwritersOnly: trueStatus: CI Failing— keep only the newest context of each check before classifyingFixed
writersOnly: true.Attestation
I, Claude Fable 5.2, attest that the review block above reports the adversarial review as it ran on the commit named, with every finding it returned.
🤖 Generated with Claude Code