mirror of
https://github.com/TeamNewPipe/NewPipe.git
synced 2024-11-22 19:12:45 +01:00
29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
<!-- 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 helps everyone considerably :)-->
|
|
|
|
#### What is it?
|
|
- [ ] Bug fix (user facing)
|
|
- [ ] Feature (user facing)
|
|
- [ ] Code base improvement (dev facing)
|
|
- [ ] Meta improvement to the project (dev facing)
|
|
|
|
#### Description of the changes in your PR
|
|
<!-- While bullet points are the norm in this section, feel free to write a text instead if you can't fit it in a list -->
|
|
- record videos
|
|
- create clones
|
|
- take over the world
|
|
|
|
#### Fixes the following issue(s)
|
|
<!-- Also add reddit or other links which are relevant to your change. -->
|
|
-
|
|
|
|
#### Relies on the following changes
|
|
<!-- Delete this if it doesn't apply to you. -->
|
|
-
|
|
|
|
#### Testing apk
|
|
<!-- Ensure that you have your changes on a new branch which has a meaningful name. This name will be used as a suffix for the app ID to allow installing and testing multiple versions of NewPipe. Do NOT name your branches like "patch-0" and "feature-1". For example, if your PR implements a bug fix for comments, an appropriate branch name would be "commentfix". -->
|
|
debug.zip
|
|
|
|
#### Agreement
|
|
- [ ] I carefully read the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) and agree to them.
|