Simplify github issue templates; correct labels

If they're too long, people won't read them.
If they're too short, people won't know what to do.
If there are too many of them, people can't decide which to use.

Removed the question template because it's redundant with "open a blank
issue".
This commit is contained in:
Henrik Lissner 2019-11-28 15:32:50 -05:00
parent 9bd8904838
commit ae80f1f67d
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
4 changed files with 29 additions and 48 deletions

View file

@ -1,22 +1,19 @@
---
name: Feature request
about: Make suggestions for improving Doom Emacs
about: It'd be cool if Doom did/had/would...
labels: is:request
title: "[REQUEST] "
assignees: ''
---
**Describe the feature**
Start with a brief 1 or 2 sentence summary of feature.
Then follow up with an extended explanation, if necessary. Here are some
suggestions on what to include:
- What is your request?
- How is it helpful?
- How is the feature used?
- How is it used?
- If the feature involves new plugins, include links to them
- iF the feature involves replacement of current functionality, describe how the
new functionality is better.
- If the feature is implemented in another editor Emacs distro:
- If the feature involves replacement of current functionality, how the new
functionality is better?
- If the feature is implemented in another editor or Emacs distro:
- Include screenshots or screencasts of it
- Include links to its implementation
- Include names of commands (and not just the keybinds to invoke them)
@ -25,4 +22,7 @@ suggestions on what to include:
**System information**
<details><pre>
Include the output of `M-x doom/info` or `~/.emacs.d/bin/doom info` here.
It's possible Doom already has the feature you're requesting. This will tell me
why you aren't seeing it.
</pre></details>