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
{{ message }}
This repository was archived by the owner on Jan 21, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
name: Bug report
2
2
description: Create a bug report to help us improve
3
-
labels: [bug]
3
+
labels: [bug, needs triage]
4
4
body:
5
5
- type: markdown
6
6
attributes:
@@ -20,6 +20,8 @@ body:
20
20
required: true
21
21
- label: "I made sure that there are *no existing issues* - [open](https://github.com/polymorphicshade/NewPipe/issues) or [closed](https://github.com/polymorphicshade/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to."
22
22
required: true
23
+
- label: "I have read the [FAQ](https://newpipe.net/FAQ/) and my problem isn't listed."
24
+
required: true
23
25
- label: "I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise."
24
26
required: true
25
27
- label: "This issue contains only one bug."
@@ -42,7 +44,7 @@ body:
42
44
label: Steps to reproduce the bug
43
45
description: |
44
46
What did you do for the bug to show up?
45
-
47
+
46
48
If you can't cause the bug to show up again reliably (and hence don't have a proper set of steps to give us), please still try to give as many details as possible on how you think you encountered the bug.
47
49
placeholder: |
48
50
1. Go to '...'
@@ -71,11 +73,11 @@ body:
71
73
label: Screenshots/Screen recordings
72
74
description: |
73
75
A picture or video is worth a thousand words.
74
-
76
+
75
77
If applicable, add screenshots or a screen recording to help explain your problem.
76
78
GitHub supports uploading them directly in the text box.
77
79
If your file is too big for Github to accept, try to compress it (ZIP-file) or feel free to paste a link to an image/video hoster here instead.
78
-
80
+
79
81
:heavy_exclamation_mark: DON'T POST SCREENSHOTS OF THE ERROR PAGE.
80
82
Instead, follow the instructions in the "Logs" section below.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.yml
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,22 @@
1
1
name: Feature request
2
2
description: Suggest an idea for this project
3
-
labels: [enhancement]
3
+
labels: [enhancement, needs triage]
4
4
body:
5
5
- type: markdown
6
6
attributes:
7
7
value: |
8
8
Thank you for helping to make NewPipe better by suggesting a feature. :hugs:
9
9
10
10
Your ideas are highly welcome! The app is made for you, the users, after all.
11
-
12
11
- type: checkboxes
13
12
id: checklist
14
13
attributes:
15
14
label: "Checklist"
16
15
options:
17
16
- label: "I made sure that there are *no existing issues* - [open](https://github.com/polymorphicshade/NewPipe/issues) or [closed](https://github.com/polymorphicshade/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to."
18
17
required: true
18
+
- label: "I have read the [FAQ](https://newpipe.net/FAQ/) and my problem isn't listed."
19
+
required: true
19
20
- label: "I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at [NewPipeExtractor](https://github.com/TeamNewPipe/NewPipeExtractor/issues)."
20
21
required: true
21
22
- label: "I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise."
@@ -54,7 +55,7 @@ body:
54
55
(This is not the place for stale upstream feature requests!)
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/question.yml
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
name: Question
2
2
description: Ask about anything NewPipe-related
3
-
labels: [question]
3
+
labels: [question, needs triage]
4
4
body:
5
5
- type: markdown
6
6
attributes:
@@ -16,6 +16,8 @@ body:
16
16
options:
17
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."
18
18
required: true
19
+
- label: "I have read the [FAQ](https://newpipe.net/FAQ/) and my question isn't listed."
20
+
required: true
19
21
- label: "I have taken the time to fill in all the required details. I understand that the question will be dismissed otherwise."
20
22
required: true
21
23
- label: "I have read and understood the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md)."
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@
25
25
<!-- Delete this if it doesn't apply to your PR. -->
26
26
-
27
27
28
-
#### APK testing
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
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.
0 commit comments