mirror of
https://github.com/TeamNewPipe/NewPipe
synced 2024-11-16 14:54:57 +00:00
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
<!-- Hey there. Thank you so much for improving NewPipe, and filling out the details. Having roughly the same layout helps everyone considerably :)-->
|
|
|
|
#### What is it?
|
|
- [ ] Bugfix (user facing)
|
|
- [ ] Feature (user facing)
|
|
- [ ] Codebase 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 free-form text instead of a list -->
|
|
- record videos
|
|
- create clones
|
|
- take over the world
|
|
|
|
#### Fixes the following issue(s)
|
|
<!-- Prefix issues with "Fixes" so that GitHub closes them when the PR is merged (note that each "Fixes #" should be in its own item). Also add any other relevant links. -->
|
|
- Fixes #
|
|
|
|
#### Relies on the following changes
|
|
<!-- Delete this if it doesn't apply to you. -->
|
|
-
|
|
|
|
#### APK testing
|
|
<!-- Use a new, meaningfully named branch. The name is used as a suffix for the app ID to allow installing and testing multiple versions of NewPipe, e.g. "commentfix", if your PR implements a bugfix for comments. (No names like "patch-0" and "feature-1".) -->
|
|
<!-- Remove the following line if you directly link the APK created by the CI pipeline. Directly linking is preferred if you need to let users test.-->
|
|
On the website the APK can be found by going to the "Checks" tab below the title and then on "artifacts" on the right.
|
|
|
|
#### Due diligence
|
|
- [ ] I read the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md).
|