29efd1e6a4
This is really essential thing that everyone should be doing. A few extra notifications won't hurt anyone, and we should be tracking issues to connect them to the best people who can handle them. Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>
44 lines
938 B
Markdown
44 lines
938 B
Markdown
---
|
|
name: Bug report
|
|
about: Create a report to help us improve
|
|
title: ''
|
|
labels: '0.kind: bug'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
**Describe the bug**
|
|
A clear and concise description of what the bug is.
|
|
|
|
**To Reproduce**
|
|
Steps to reproduce the behavior:
|
|
1. ...
|
|
2. ...
|
|
3. ...
|
|
|
|
**Expected behavior**
|
|
A clear and concise description of what you expected to happen.
|
|
|
|
**Screenshots**
|
|
If applicable, add screenshots to help explain your problem.
|
|
|
|
**Additional context**
|
|
Add any other context about the problem here.
|
|
|
|
**Notify maintainers**
|
|
<!--
|
|
Please @ people who are in the `meta.maintainers` list of the offending package or module.
|
|
If in doubt, check `git blame` for whoever last touched something.
|
|
-->
|
|
|
|
**Metadata**
|
|
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
|
|
|
|
Maintainer information:
|
|
```yaml
|
|
# a list of nixpkgs attributes affected by the problem
|
|
attribute:
|
|
# a list of nixos modules affected by the problem
|
|
module:
|
|
```
|