From 0e16eaeb817b653758637329056227e76e6966ca Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Thu, 22 Oct 2026 11:25:42 -0400 Subject: [PATCH] feat(intake): let intake apply needs-human on a re-entered issue Add allowed-labels to the intake caller: the reusable's defaults plus needs-human. A re-entered issue that still needs a person now gets the plain label and keeps the run's own comment (quoted decision, new questions) instead of the fixed escalation note. Closes #8491 Co-Authored-By: Claude Opus 5.5 --- .github/workflows/intake-triage.yml | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/.github/workflows/intake-triage.yml b/.github/workflows/intake-triage.yml index cc99826adb..3ba0ebeca0 100644 --- a/.github/workflows/intake-triage.yml +++ b/.github/workflows/intake-triage.yml @@ -189,7 +189,21 @@ jobs: # Re-entry after a recorded decision (intake-reenter.yml). The marker is # the first line isDecisionComment in select-trusted-text.mjs matches. An # escalated run posts only the reusable's fixed note, so the quote and - # new questions survive only on a run that does not set needs_human. + # new questions survive only on a run that does not set needs_human, so + # allowed-labels lets the run apply `needs-human` as a plain label (the + # reusable's defaults plus that label). + allowed-labels: | + priority: critical + priority: high + priority: medium + priority: low + status: needs-info + status: needs-decision + question + area: security + good first issue + help wanted + needs-human instructions: | RE-ENTRY AFTER A RECORDED DECISION. Apply this section only when a comment's first line is exactly `**Decision recorded.**` and whose author login does not end in `[bot]`; the newest @@ -209,8 +223,9 @@ jobs: After the quote, ask each as a numbered new question with a `RECOMMENDED:` answer and its basis. Never fill one with a default of your own or treat a recommendation as decided. d. When the remaining work needs a person (a host, spend, a trust-boundary call, or an - attended run), set needs_human true, even when (c) also applies. The decision comment - stays on the issue for the person who picks it up. + attended run), apply the `needs-human` label and keep needs_human false, even when (c) + also applies, so your comment with the quote and new questions is kept. The decision + comment stays on the issue for the person who picks it up. e. When the decision settles every open question and no person is needed, apply no status label, quote the decision, say in one sentence that it settles the open questions, and ask nothing again. Triage the rest as usual.