Skip to content

Say what needs-triage and ready-for-human mean once a Triage Pass runs - #1966

Merged
JacobStephens2 merged 1 commit into
mainfrom
triage-labels-docs
Nov 10, 2026
Merged

JacobStephens2 merged 1 commit into
mainfrom
triage-labels-docs

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Docs only: docs/agents/triage-labels.md.

  • needs-triage now reads as a queue a scheduled Triage Pass may work unattended. With triage.allow_ready_for_agent on, that can end in a Self-merged change.
  • ready-for-human covers decisions, shaping, access and security judgement, not only implementation.
  • A new section, "Choosing between needs-triage and ready-for-human", lists when to use which, and points at A Triage Pass doesn't wait for an issue to settle, so it can triage a Spec before its Tickets are published #1965: a Triage Pass doesn't wait for an issue to settle, so it can take a Spec before its Tickets are attached.

Not changed: the GitHub label descriptions in src/labels.rs still use the old wording.

needs-triage is now a queue a scheduled Triage Pass may work unattended,
and ready-for-human covers decisions, shaping and access, not only
implementation. Point at #1965 for the settling gap.
@JacobStephens2
JacobStephens2 merged commit 014196b into main Nov 10, 2026
4 checks passed
@JacobStephens2
JacobStephens2 deleted the triage-labels-docs branch November 10, 2026 19:14
This was referenced Nov 10, 2026
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