mirror of
https://github.com/schpet/linear-cli.git
synced 2026-09-14 14:26:50 +08:00
Peter Schilling
e8a7cd4668
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.
31 lines
988 B
YAML
31 lines
988 B
YAML
name: Feature request
|
|
description: Propose a change to linear-cli.
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Issues are for bugs and feature requests in linear-cli. Usage questions belong in [Discussions](https://github.com/schpet/linear-cli/discussions). See [CONTRIBUTING.md](https://github.com/schpet/linear-cli/blob/main/CONTRIBUTING.md) for what is in scope.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem
|
|
description: What were you trying to do, and what got in the way? Describe the use case, not only the fix you have in mind.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed change
|
|
description: What you would like linear-cli to do.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: Workarounds or other approaches you looked at.
|