From 4cdd8035a788619746694a6a1b0154b0346b6d4d Mon Sep 17 00:00:00 2001 From: mrsibe Date: Fri, 25 Sep 2026 13:07:09 +0800 Subject: [PATCH] chore(github): add a Discussions contact link to the issue templates MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ideas and workflow pain points now have a channel that is not the issue tracker, but nothing pointed to it. The issue chooser offered only "Bug Report", "Feature Request" and a blank issue, so the feedback that #11 collects would still have arrived as issues after Discussions was enabled. The Ideas category is now linked from the chooser, with the same wording the discussion itself uses, and it states what happens to an idea afterwards — it moves into its own issue with an owner, acceptance criteria and a milestone. That promise is the reason to route ideas here rather than through #11: an idea posted as a discussion can be converted into tracked work without the author restating it, which is not true of a comment buried in a long thread. `blank_issues_enabled` stays true, and the comment is rewritten because its original rationale — "plenty of feedback does not fit cleanly into bug or feature" — is now partly answered by Discussions, while a blank issue remains the right shape for a wrong claim in the README or a packaging surprise. No change to which templates are offered. --- .github/ISSUE_TEMPLATE/config.yml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index cdeff69..ff8ce8c 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,4 +1,15 @@ -# Blank issues stay enabled while the project is small: plenty of feedback does -# not fit cleanly into "bug" or "feature". Revisit once issue volume is high -# enough that unfilled reports start costing triage time. +# Blank issues stay enabled. Bug reports and feature requests have templates, and +# ideas and workflow pain points now have a home in Discussions, but a blank issue +# is still the right shape for the things that fit neither — a wrong claim in the +# README, a packaging surprise, a question about the architecture. Revisit once +# issue volume is high enough that unfilled reports start costing triage time. blank_issues_enabled: true + +contact_links: + # Ideas and workflow pain points are collected as discussions, so that an early + # idea does not have to arrive fully specified. Once something is approved as + # work it moves into its own issue, with an owner, acceptance criteria and a + # milestone. + - name: Feature requests & workflow pain points + url: https://github.com/mrsibe/KnowNote/discussions/categories/ideas + about: Suggest an idea, or describe a workflow that is harder than it should be. Approved work moves into its own issue.