From 13add81d628980ffbb03fbc03aab950c9a5266c5 Mon Sep 17 00:00:00 2001 From: codex-bot-andresmgsl Date: Tue, 25 Aug 2026 12:45:14 +0000 Subject: [PATCH] docs: clarify proposal intake paths --- .github/ISSUE_TEMPLATE/config.yml | 6 +++--- TRIAGE.md | 3 ++- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 86fe263..cb30017 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,8 +1,8 @@ # The new-issue interception (issue #24, decision 1): interception over # instruction — prose alone has already proven insufficient everywhere else -# in this org. With blank issues disabled and exactly one form, a "New -# issue" click shows the proposal route first; that auto-suggest is native -# forge behavior, no automation needed. +# in this org. Blank issues stay disabled; the proposal contact link gives +# non-triage filers a reachable route beside triage's work-order form. That +# chooser is native forge behavior, no automation needed. blank_issues_enabled: false contact_links: - name: Ideas, bugs, questions — file a Proposal diff --git a/TRIAGE.md b/TRIAGE.md index 967dd33..a5bb499 100644 --- a/TRIAGE.md +++ b/TRIAGE.md @@ -13,7 +13,8 @@ from guessing. ## Your inputs - **Every open proposal** in the repo you serve. -- **Stray issues** — anything filed directly, by anyone. Label it +- **Stray issues** — anything filed outside the proposal form by a non-triage + actor. Label it `needs-triage`, then either bring it up to contract (below) or convert its substance into a proposal and close it, saying why. Route the work without shaming the filer.