github: update issue templates
This commit is contained in:
14
.github/ISSUE_TEMPLATE/feature-request.md
vendored
14
.github/ISSUE_TEMPLATE/feature-request.md
vendored
@ -1,13 +1,13 @@
|
||||
---
|
||||
name: Mu4e Feature request
|
||||
about: Suggest an idea for this project
|
||||
title: "[mu4e rfe]"
|
||||
labels: rfe, mu4e, new
|
||||
name: Feature request
|
||||
about: Suggest an idea for mu or mu4e
|
||||
title: "[RFE]"
|
||||
labels: rfe, new
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
Note, please see the IDEAS.org file in repository root for existing ideas;
|
||||
maybe it's already there.
|
||||
|
||||
Note, please see the IDEAS.org file in repository root for existing ideas; maybe
|
||||
it's already there.
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
22
.github/ISSUE_TEMPLATE/mu-bug-report.md
vendored
22
.github/ISSUE_TEMPLATE/mu-bug-report.md
vendored
@ -4,17 +4,29 @@ about: Create a report to help us improve
|
||||
title: "[mu bug]"
|
||||
labels: bug, mu, new
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Describe the bug**
|
||||
A clear and concise description of what the bug is, what you expected to happen and what actually happened.
|
||||
|
||||
**To Reproduce**
|
||||
Detailed steps to reproduce the behavior. If this is about a specific (kind of) message, **always** attach an (anonymized as need) example message.
|
||||
Give the bug a good title.
|
||||
|
||||
Please provide a clear and concise description of what you expected to happen
|
||||
and what actually happened, and follow the steps below.
|
||||
|
||||
**How to Reproduce**
|
||||
|
||||
Include the exact steps of what you were doing (commands executed etc.). Include
|
||||
any relevant logs and outputs.
|
||||
|
||||
Does the problem happen each time? Sometimes?
|
||||
|
||||
If this is about a specific (kind of) message, please attach an example message
|
||||
(anonymized as needed)
|
||||
|
||||
**Environment**
|
||||
Please describe the versions of OS, Emacs, mu etc. you are using.
|
||||
|
||||
**Checklist**
|
||||
- [ ] you are running either the latest 1.8.x/1.10.x release or `master` (otherwise, please upgrade).
|
||||
- [ ] you are running either the latest 1.10.x/1.12.x release or `master` (otherwise, please upgrade).
|
||||
|
||||
Thank you!
|
||||
|
||||
5
.github/ISSUE_TEMPLATE/mu4e-bug-report.md
vendored
5
.github/ISSUE_TEMPLATE/mu4e-bug-report.md
vendored
@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Mu4e Bug Report
|
||||
about: Create a report to help us improve
|
||||
about: Create a report to help us improve mu4e
|
||||
title: "[mu4e bug]"
|
||||
labels: bug, mu4e, new
|
||||
assignees: ''
|
||||
@ -21,6 +21,9 @@ any relevant logs and outputs:
|
||||
- Best start from `emacs -Q`, and load a minimal `mu4e` setup; describe the steps
|
||||
that lead up to the bug.
|
||||
- Does the problem happen each time? Sometimes?
|
||||
|
||||
- Try some small variations of what you were doing. Does it make a difference?
|
||||
|
||||
- If this is about a specific (kind of) message, attach an example message.
|
||||
(Open the message, press `.` (`mu4e-view-raw-message`), then `C-x C-w` and
|
||||
attach. Anonymize as needed, all that matters is that the issue still
|
||||
|
||||
Reference in New Issue
Block a user