Merge branch 'templates' of https://github.com/Poolitzer/NewPipe into templates
This commit is contained in:
poolitzer
commit
e2cb927e1f
|
|
@ -15,8 +15,9 @@ Use this template to notify us if you found a bug.
|
|||
To make it easier for us to help you please enter detailed information below.
|
||||
|
||||
Please note, we only support the latest version of NewPipe and
|
||||
master branch. Please make sure to upgrade & recreate the issue on the latest
|
||||
version prior to opening an issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is a good start, make sure its version is the same as in you app (To check you version, press on the three line menu on the left, click on "About", and you will see your current version.)
|
||||
master branch. Please make sure to upgrade & recreate the issue on the latest version prior to opening an issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is a good start, make sure its version is the same as in you app (To check you version, press on the three line menu on the left, click on "About", and you will see your current version).
|
||||
|
||||
P.S.: Our [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) might be a nice document to read before you fill out the report :)
|
||||
-->
|
||||
### Version
|
||||
<!--Which version are you using?-->
|
||||
|
|
@ -34,7 +35,7 @@ Steps to reproduce the behavior:
|
|||
Tell us what you expected to happen.
|
||||
|
||||
### Actual behaviour
|
||||
Tell us what happens instead
|
||||
Tell us what happens instead.
|
||||
|
||||
### Screenshots/-recording
|
||||
If applicable, add screenshots or a screen recording to help explain your problem. Github should support uploading them directly in the issue field. If your file is too big, feel free to paste a link from a image/video hoster here instead.
|
||||
|
|
@ -42,4 +43,4 @@ If applicable, add screenshots or a screen recording to help explain your proble
|
|||
### Logs
|
||||
If your bug includes a crash, please head over to the [incredible bugreport to markdown converter](https://teamnewpipe.github.io/CrashReportToMarkdown/). Copy the result. Paste it here:
|
||||
|
||||
<!--Thats right, here-->
|
||||
<!--That's right, here-->
|
||||
|
|
|
|||
|
|
@ -6,24 +6,25 @@ labels: enhancement
|
|||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
<!-- Hey. Our [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) might be a nice
|
||||
document to read before you fill out the request :) -->
|
||||
#### Is your feature request related to a problem? Please describe.
|
||||
A clear and concise description of what the problem is.
|
||||
Ex. *I want to do X, but there is no way to do it.*
|
||||
Example: *I want to do X, but there is no way to do it.*
|
||||
|
||||
#### Describe the solution you'd like
|
||||
A clear and concise description of what you want to happen.
|
||||
Ex. *I think it would be nice if you would add feature Y so it will make it easier.*
|
||||
Example: *I think it would be nice if you would add feature Y so it will make it easier.*
|
||||
|
||||
#### Describe alternatives you've considered
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
Ex. *I considered Z, but that didn't work because...*
|
||||
Example: *I considered Z, but that didn't work because...*
|
||||
|
||||
#### Additional context
|
||||
Add any other context or screenshots about the feature request here.
|
||||
Ex. *Here's a photo of my cat!*
|
||||
Example: *Here's a photo of my cat!*
|
||||
|
||||
#### Why do you/everyone wants this feature
|
||||
Convince us! How does it change your NewPipe experience and/or your life?
|
||||
The better this paragraph is, the more likely a developer will think about developing it
|
||||
The better this paragraph is, the more likely a developer will think about developing it.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Hey there. Thank you so much for improving our app. Please take a moment to fill out the following suggestion on how to structure this PR description. Having roughly the same layout drastically helps everybody :)-->
|
||||
<!-- Hey there. Thank you so much for improving NewPipe. Please take a moment to fill out the following suggestion on how to structure this PR description. Having roughly the same layout drastically helps everybody :)-->
|
||||
|
||||
#### What is it?
|
||||
- [ ] Bug fix
|
||||
|
|
@ -16,7 +16,7 @@
|
|||
-
|
||||
|
||||
#### Testing apk
|
||||
<!--Please add ".branchname" at the end of the app signature, only if the current branch name is not "master" or "dev".-->
|
||||
<!--Ensure to have your changes on a new branch which has a meaningful name. This name will be used as suffix of the app id to allow installing and testing multiple versions of NewPipe. Do NOT name your branches like "patch-0" and "feature-1".-->
|
||||
debug.zip
|
||||
|
||||
#### Agreement
|
||||
|
|
|
|||
Loading…
Reference in New Issue