You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/CONTRIBUTING.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
### Please do **not** open pull requests for *new features* now, as we are planning to rewrite large chunks of the code. Only bugfix PRs will be accepted. More details will be announced soon!
2
+
1
3
NewPipe contribution guidelines
2
4
===============================
3
5
@@ -40,10 +42,6 @@ You'll see *exactly* what is sent, be able to add **your comments**, and then se
40
42
* Create PRs that cover only **one specific issue/solution/bug**. Do not create PRs that are huge monoliths and could have been split into multiple independent contributions.
41
43
* NewPipe uses [NewPipeExtractor](https://github.com/TeamNewPipe/NewPipeExtractor) to fetch data from services. If you need to change something there, you must test your changes in NewPipe. Telling NewPipe to use your extractor version can be accomplished by editing the `app/build.gradle` file: the comments under the "NewPipe libraries" section of `dependencies` will help you out.
42
44
43
-
### Kotlin in NewPipe
44
-
* NewPipe will remain mostly Java for time being
45
-
* Contributions containing a simple conversion from Java to Kotlin should be avoided. Conversions to Kotlin should only be done if Kotlin actually brings improvements like bug fixes or better performance which are not, or only with much more effort, implementable in Java. The core team sees Java as an easier to learn and generally well adopted programming language.
46
-
47
45
### Creating a Pull Request (PR)
48
46
49
47
* Make changes on a **separate branch** with a meaningful name, not on the _master_ branch or the _dev_ branch. This is commonly known as *feature branch workflow*. You may then send your changes as a pull request (PR) on GitHub.
Copy file name to clipboardexpand all lines: .github/DISCUSSION_TEMPLATE/questions.yml
+2-5
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,8 @@
1
-
name: Question
2
-
description: Ask about anything NewPipe-related
3
-
labels: [question, needs triage]
4
1
body:
5
2
- type: markdown
6
3
attributes:
7
4
value: |
8
-
Thanks for taking the time to fill out this issue! :hugs:
5
+
Thanks for taking the time to fill out this form! :hugs:
9
6
10
7
Note that you can also ask questions on our [IRC channel](https://web.libera.chat/#newpipe).
11
8
@@ -14,7 +11,7 @@ body:
14
11
attributes:
15
12
label: "Checklist"
16
13
options:
17
-
- label: "I made sure that there are *no existing issues* - [open](https://github.com/TeamNewPipe/NewPipe/issues) or [closed](https://github.com/TeamNewPipe/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to."
14
+
- label: "I made sure that there are *no existing issues or discussions* - [open](https://github.com/TeamNewPipe/NewPipe/issues) or [closed](https://github.com/TeamNewPipe/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to."
18
15
required: true
19
16
- label: "I have read the [FAQ](https://newpipe.net/FAQ/) and my question isn't listed."
Copy file name to clipboardexpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+1-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ body:
14
14
attributes:
15
15
label: "Checklist"
16
16
options:
17
-
- label: "I am able to reproduce the bug with the [latest version](https://github.com/TeamNewPipe/NewPipe/releases/latest)."
17
+
- label: "I am able to reproduce the bug with the latest version given here: [CLICK THIS LINK](https://github.com/TeamNewPipe/NewPipe/releases/latest)."
18
18
required: true
19
19
- label: "I made sure that there are *no existing issues* - [open](https://github.com/TeamNewPipe/NewPipe/issues) or [closed](https://github.com/TeamNewPipe/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to."
Copy file name to clipboardexpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@
28
28
#### APK testing
29
29
<!-- 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".) -->
30
30
<!-- 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.-->
31
-
The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR.
31
+
The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR. You can find more info and a video demonstration [on this wiki page](https://github.com/TeamNewPipe/NewPipe/wiki/Download-APK-for-PR).
32
32
33
33
#### Due diligence
34
34
-[ ] I read the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md).
0 commit comments