Add issue templates and CONTRIBUTING with tracker scope - #273
Merged
Conversation
schpetbot
force-pushed
the
issue-tracker-scope
branch
2 times, most recently
from
September 1, 2026 03:37
def2075 to
a549098
Compare
The issue tracker occasionally gets unsolicited issues promoting the author's own npm package rather than reporting a problem with linear-cli. State the tracker's scope up front so closing those cites a rule instead of an ad-hoc judgment call. Issue forms replace free-form issues: their required problem and reproduction fields are the friction that actually helps, by asking for the thing a promotional issue does not have. Usage questions route to Discussions; nothing routes package promotion anywhere.
schpetbot
force-pushed
the
issue-tracker-scope
branch
from
September 1, 2026 03:38
a549098 to
0536dbe
Compare
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
2 participants
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.
The repo has no issue templates or contributing guide, so every issue starts as a blank box with no stated scope. This adds both, to cut down on off-topic issues and to make the tracker's purpose clear before someone starts typing.
What this adds
.github/ISSUE_TEMPLATE/config.yml— disables blank issues, routes usage questions to Discussions.github/ISSUE_TEMPLATE/bug-report.yml— required: what happened, repro steps, version, environment.github/ISSUE_TEMPLATE/feature-request.yml— required: the problem hit, then the proposalCONTRIBUTING.md— a scope section, plus a short dev/PR section using the existingdeno tasknamesScope
The tracker is for bugs and feature requests in linear-cli, from people using it. Usage questions go to Discussions. On dependency recommendations,
CONTRIBUTING.mdasks directly:Having this written down means out-of-scope issues get closed by citing a rule rather than an ad-hoc judgment call each time.
Notes
There is deliberately no "I have read the guidelines" acknowledgement checkbox. It gets ticked without friction by anyone it is aimed at, while legitimate reporters get a meaningless hurdle. The useful friction is the required problem field, since it asks for the one thing an off-topic issue does not have.
blank_issues_enabled: falseremoves the blank-issue link from the chooser, but/issues/newstill works for anyone who navigates there directly. It shapes the default path rather than closing it off.https://claude.ai/code/session_0131SpUmPyWhkVGNTDHFUkPu