1
0
mirror of https://github.com/TeamNewPipe/NewPipe synced 2024-12-14 12:50:33 +01:00
NewPipe/.github/PULL_REQUEST_TEMPLATE.md

29 lines
1.3 KiB
Markdown
Raw Normal View History

2020-03-03 05:52:50 +01:00
<!-- 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 :)-->
2020-02-23 05:16:14 +01:00
2020-02-24 01:16:18 +01:00
#### What is it?
- [ ] Bug fix (user facing)
- [ ] Feature (user facing)
- [ ] Code base improvement (dev facing)
- [ ] Meta improvement to the project (dev facing)
2020-02-24 01:16:18 +01:00
#### Description of the changes in your PR
2020-03-03 05:52:50 +01:00
<!-- 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
2020-02-23 05:16:14 +01:00
#### Fixes the following issue(s)
2020-03-03 05:52:50 +01:00
<!-- Also add reddit or other links which are relevant to your change. -->
2020-02-24 01:16:18 +01:00
-
2020-02-23 05:16:14 +01:00
#### Relies on the following changes
<!-- Delete this if it doesn't apply to you. -->
2020-02-24 01:16:18 +01:00
-
2020-02-23 05:16:14 +01:00
#### 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". -->
2020-02-23 05:16:14 +01:00
debug.zip
#### Agreement
- [ ] I carefully read the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) and agree to them.