Auto merge of #4384 - str4d:issue-templates, r=str4d
Migrate to new GitHub issue template workflow New templates are added for feature requests and UX reports.
This commit is contained in:
Homu
commit
2a6be9fd19
|
|
@ -1,10 +1,27 @@
|
|||
<!--- Remove text and sections that do not apply -->
|
||||
---
|
||||
name: Bug report
|
||||
about: Create a report about a bug in zcashd.
|
||||
title: ''
|
||||
labels: 'bug'
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
<!--
|
||||
This issue tracker is only for technical issues related to zcashd.
|
||||
|
||||
General Zcash questions and/or support requests and are best directed to the [Zcash Forums](https://forum.z.cash) or [Community Rocket.Chat](https://chat.zcashcommunity.com).
|
||||
General Zcash questions and/or support requests and are best directed to the
|
||||
Zcash Forum: https://forum.zcashcommunity.com/
|
||||
|
||||
For reporting security vulnerabilities or for sensitive discussions with our security team, please contact [security@z.cash](mailto:security@z.cash). You can use the [GPG key](https://z.cash/gpg-pubkeys/security.asc) (fingerprint: `AF85 0445 546C 18B7 86F9 2C62 88FB 8B86 D8B5 A68C`) to send an encrypted message. The key and fingerprint are duplicated on our [Public Keys page](https://z.cash/support/pubkeys.html).
|
||||
For reporting security vulnerabilities or for sensitive discussions with our
|
||||
security team, please email security@z.cash . You can use this GPG key to send
|
||||
an encrypted message:
|
||||
https://z.cash/gpg-pubkeys/security.asc
|
||||
fingerprint: AF85 0445 546C 18B7 86F9 2C62 88FB 8B86 D8B5 A68C
|
||||
|
||||
The key and fingerprint are duplicated on our Public Keys page:
|
||||
https://z.cash/support/pubkeys.html
|
||||
-->
|
||||
|
||||
### Describe the issue
|
||||
Please provide a general summary of the issue you're experiencing
|
||||
|
|
@ -19,7 +36,8 @@ Please provide a general summary of the issue you're experiencing
|
|||
Tell us what should happen
|
||||
|
||||
### Actual behaviour + errors
|
||||
Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
|
||||
Tell us what happens instead including any noticable error output (any messages
|
||||
displayed on-screen when e.g. a crash occurred)
|
||||
|
||||
### The version of Zcash you were using:
|
||||
Run `zcashd --version` to find out
|
||||
|
|
@ -36,9 +54,12 @@ Run `zcashd --version` to find out
|
|||
- Assembler version (as --version):
|
||||
|
||||
### Any extra information that might be useful in the debugging process.
|
||||
This includes the relevant contents of `~/.zcash/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
|
||||
Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
|
||||
This includes the relevant contents of `~/.zcash/debug.log`. You can paste raw
|
||||
text, attach the file directly in the issue or link to the text via a pastebin
|
||||
type site. Please also include any non-standard things you did during
|
||||
compilation (extra flags, dependency version changes etc.) if applicable.
|
||||
|
||||
### Do you have a backup of `~/.zcash` directory and/or take a VM snapshot?
|
||||
- Backing up / making a copy of the `~/.zcash` directory might help make the problem reproducible. Please redact appropriately.
|
||||
- Backing up / making a copy of the `~/.zcash` directory might help make the
|
||||
problem reproducible. Please redact appropriately.
|
||||
- Taking a VM snapshot is really helpful for interactively testing fixes
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
name: Feature request
|
||||
about: Suggest an idea for zcashd.
|
||||
title: ''
|
||||
labels: 'use case'
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Is your feature request related to a problem? Please describe.
|
||||
A clear and concise description of what the problem is. Example: I'm always
|
||||
frustrated when [...]
|
||||
|
||||
## Describe the solution you'd like
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
## Alternatives you've considered
|
||||
A clear and concise description of any alternative solutions or features you've
|
||||
considered.
|
||||
|
||||
## Additional context
|
||||
Add any other context or screenshots about the feature request here.
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
name: UX report
|
||||
about: Was zcashd hard to use? It's not you, it's us. We want to hear about it.
|
||||
title: 'UX: '
|
||||
labels: 'usability'
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
<!-- Did zcashd not do what you expected?
|
||||
Was it hard to figure out how to do something?
|
||||
Could an error message be more helpful?
|
||||
It's not you, it's us. We want to hear about it. -->
|
||||
|
||||
## What were you trying to do
|
||||
|
||||
## What happened
|
||||
Loading…
Reference in New Issue