github: Cleanup issue templates

We no longer allow people to create issues from a blank template.

The templates for bug reports and build issues are also much more
explicit in what they want from the user.
This commit is contained in:
patrick96 2020-11-26 20:20:29 +01:00 committed by Patrick Ziegler
parent 2f549575c7
commit 9d31b51a63
4 changed files with 58 additions and 26 deletions

View File

@ -4,41 +4,58 @@ about: Create a report for something that misbehaves
---
## Describe the issue
*A clear and concise description of what the bug is.*
## Checklist
<!-- Please carefully go through this checklist and put an 'x' inside the brackets: '[x]' -->
* [ ] I have read the appropriate section in the [contributing
guidelines](https://github.com/polybar/polybar/blob/master/CONTRIBUTING.md)
* [ ] I believe this issue is a problem with polybar itself and not a misconfiguration on my part.
* [ ] I have searched for other open and closed [issues](https://github.com/polybar/polybar/issues?q=is%3Aissue) that
may have already reported this problem.
* [ ] I have checked the [known issues](https://github.com/polybar/polybar/wiki/Known-Issues) page for this problem.
## Describe the bug
<!-- A clear and concise description of what the bug is: -->
**Expected behavior:**
<!-- A clear and concise description of what you expected to happen: -->
*A clear and concise description of what you expected to happen.*
**Actual behavior:**
<!-- What actually happens: -->
*What actually happens*
**Was it working before?**
* Did you also experience this bug in an earlier version of polybar?
* Did you also experience this bug in an earlier version of polybar (yes/no/don't know)?
* If no, what was the last version where this worked correctly?
## To Reproduce
*A minimal but complete config with which the problem occurs:*
<!-- A minimal but complete config with which the problem occurs: -->
```dosini
```
*List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.*
<!-- List any other steps needed to reproduce the issue, besides starting polybar with the config you posted above. -->
## Polybar Log
*Post everything polybar outputs to the terminal when you run it and the issue occurs below*
<!-- Post everything polybar outputs to the terminal when you run it and the issue occurs below -->
```
```
## Screenshots
*If applicable, add screenshots to help explain your problem.*
<!-- If applicable, add screenshots to help explain your problem. -->
## Environment:
* WM:
* Distro:
* Output of `polybar -vvv`:
```
```
## Additional context
*Add any other context that you think is necessary about the problem here.*
<!-- Add any other context that you think is necessary about the problem here. -->

View File

@ -1,25 +1,40 @@
---
name: Build Issues
about: Report issues while building polybar
about: Report issues while building polybar from source
---
## Checklist
<!-- Please carefully go through this checklist and put an 'x' inside the brackets: '[x]' -->
* [ ] I have followed every step on the [compiling wiki page](https://github.com/polybar/polybar/wiki/Compiling) and
installed all necessary dependencies.
* [ ] My problem is not described on the [known issues page](https://github.com/polybar/polybar/wiki/Known-Issues)
* [ ] I have searched for other open and closed [issues](https://github.com/polybar/polybar/issues?q=is%3Aissue) that
may have already reported this problem.
* [ ] I was able to reproduce this build issue in a clean build
## Build Process
*Describe how you build polybar, list the exact commands you are using:*
**How did you build polybar?**
<!--
Put an 'x' inside the brackets ([x]) of the entry that applies and respond to the question inside the parenthesis
-->
**If you build polybar directly from this repository:**
* [ ] From a release archive (Which version?)
* [ ] By cloning this repository (What is the of `git describe --tags`?)
* [ ] Some other way (How?)
* Output of `git describe --tags`:
**If you use some other way (like the AUR):**
*List exactly where you are building from and which version you are building.*
<!-- List the exact commands you are using to build polybar: -->
## Build Log
*Post everything that is output to the terminal while building polybar below. This HAS to include the output of the `cmake` and `make` commands, if you used them.*
<!--
Copy-paste all the terminal output produced while building polybar.
This MUST include the output of the `cmake`, `make`, and/or `build.sh` commands, if you used them.
-->
```
```
@ -28,4 +43,4 @@ about: Report issues while building polybar
* Distro (with Version):
## Additional context
*Add any other context that you think is necessary about the problem here.*
<!-- Add any other context that you think is necessary about the problem here. -->

View File

@ -1,4 +1,4 @@
blank_issues_enabled: true
blank_issues_enabled: false
contact_links:
- name: Polybar Gitter Room
url: https://gitter.im/polybar/polybar

View File

@ -5,16 +5,16 @@ about: Suggest an idea for this project
---
## 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 [...]*
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
## Why does polybar need this feature?
*Describe why this feature would be useful to a large percentage of users (You need to convince us).*
<!-- Describe why this feature would be useful to a large percentage of users (You need to convince us). -->
## Describe the solution you'd like
*A clear and concise description of how your solution would work. This includes possible config options that should be added.*
<!-- A clear and concise description of how your solution would work. This includes possible config options that should be added. -->
## Describe alternatives you've considered
*A clear and concise description of any alternative solutions or features you've considered, if any.*
<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->
## Additional context
*Add any other context or screenshots about the feature request here.*
<!-- Add any other context or screenshots about the feature request here. -->