f2935e4008
- Use same multi-lined comment convention - Highlight that "additional information" in a bug report is optional - Remove recommendation for pasting script in a bug report as it's too long - Rename feature request issue file to follow same naming convention - Document also creating a issue as a way to extend scripts - Add reproduction steps in script bug reports - Use names instead of commands in heading
37 lines
788 B
Markdown
37 lines
788 B
Markdown
---
|
|
name: Feature request
|
|
about: Suggest an idea for privacy.sexy
|
|
labels: enhancement
|
|
---
|
|
|
|
<!--
|
|
Thank you for suggesting an idea to improve privacy better 🤗.
|
|
Please fill in as much of the template below as you're able.
|
|
-->
|
|
|
|
### Problem description
|
|
|
|
<!--
|
|
What are we trying to solve?
|
|
Please add a clear and concise description of the problem you are seeking to solve with this feature request.
|
|
E.g. I'm always frustrated when [...]
|
|
-->
|
|
|
|
### Proposed solution
|
|
|
|
<!--
|
|
Describe the solution you'd like in a clear and concise manner.
|
|
-->
|
|
|
|
### Alternatives considered
|
|
|
|
<!--
|
|
A clear and concise description of any alternative solutions or features you've considered.
|
|
-->
|
|
|
|
### Additional information
|
|
|
|
<!--
|
|
If applicable, add any other context or screenshots about the feature request here.
|
|
-->
|