Repository navigation
labels.trusted_labelers: let a listed app's bot hand work over by label (0.4.0) - #6
Merged
Merged
Conversation
…er by label (0.4.0) GitHub reports no role for an app's bot user, so until now a label applied by another agent was always untrusted. A source can now list logins whose labels count whatever GitHub reports. Co-Authored-By: Claude & Lothrop (cycle.five@proton.me)
… relabel by a listed bot Co-Authored-By: Claude & Lothrop (cycle.five@proton.me)
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.
What this is
0.3.0 hands work to an agent by label, and trusts a label only when GitHub reports triage access or more for whoever applied it. GitHub reports no access at all for a GitHub App's bot user, so a label applied by another agent was always
untrusted-label. That already happened in practice: an agent's app asked another agent for review by label, and the request could not be routed.Change
A source's
labelsblock gains an optional list:nameorname[bot], matched in any case. Anything else, or a duplicate, is a config error.skip_self).Listing a bot means whoever can steer that agent can route work to this mailbox, for both labels, in any repository of the organisation. The README says so.
Design:
docs/superpowers/specs/2026-11-20-label-claims-design.md, "Trust". Released as 0.4.0; the door moves with it, with no change in behaviour.Checked
cargo fmt,cargo clippy -D warnings,cargo test --workspace(193 tests), the wasm32 build, the door's typecheck and tests.After merge
Add the list to each mailbox in the manifest,
npm run mailbox -- deploy --mailroom, deploy the door, verify, tagv0.4.0, release.🤖 Generated with Claude Code
https://claude.ai/code/session_017zqkE8grD6nh1bNnb2r1X8