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
<!-- YOU HAVE TO MODIFY THIS TEXT TO FIT YOUR PR. OTHERWISE, YOUR PR WILL BE CLOSED WITHOUT FURTHER COMMENT. -->
2
-
3
-
Describe the changes you have made here: what, why, ...
1
+
<!-- YOU HAVE TO MODIFY THE TEXT BELOW TO FIT YOUR PR. OTHERWISE, YOUR PR WILL BE CLOSED WITHOUT FURTHER COMMENT. -->
4
2
5
3
<!-- LINK THE ISSUE WITH THE "Closes" KEYWORD -->
6
-
<!-- Example: Closes (link) OR Closes #xyz -->
4
+
<!-- Example: Closes (link) OR Closes #12345 -->
5
+
6
+
Closes _____
7
+
Describe the changes you have made here: what, where, why, ...
8
+
If your work is not yet complete, please open a draft pull request. In that case, outline your intended next steps. Do you need feedback? Will you continue in parallel? ...
7
9
8
10
### Mandatory checks
9
11
10
12
<!--
11
-
- Go through the list below. Please don't remove any items.
12
-
- [x] done; [ ] not done / not applicable
13
+
Go throgh the checklist below. It is mandatory, even for a draft pull request.
14
+
15
+
Keep ALL the items. Mark them as follows:
16
+
[x] done
17
+
[ ] not done
18
+
[/] not applicable
13
19
-->
14
20
15
-
-[x] I own the copyright of the code submitted and I licence it under the [MIT license](https://github.com/JabRef/jabref/blob/main/LICENSE)
21
+
-[x] I own the copyright of the code submitted and I license it under the [MIT license](https://github.com/JabRef/jabref/blob/main/LICENSE)
16
22
-[ ] Change in `CHANGELOG.md` described in a way that is understandable for the average user (if change is visible to the user)
17
23
-[ ] Tests created for changes (if applicable)
18
24
-[ ] Manually tested changed features in running JabRef (always required)
19
-
-[ ] Screenshots added in PR description (for UI changes)
25
+
-[ ] Screenshots added in PR description (if change is visible to the user)
20
26
-[ ][Checked developer's documentation](https://devdocs.jabref.org/): Is the information available and up to date? If not, I outlined it in this pull request.
21
27
-[ ][Checked documentation](https://docs.jabref.org/): Is the information available and up to date? If not, I created an issue at <https://github.com/JabRef/user-documentation/issues> or, even better, I submitted a pull request to the documentation repository.
Copy file name to clipboardexpand all lines: .github/ghprcomment.yml
+34-15
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,24 @@
1
+
- jobName: 'Source branch is other than "main"'
2
+
message: >
3
+
You committed your code on `main` brach. This is bad practise.
4
+
5
+
6
+
Please start with a proper branch name.
7
+
See [https://github.com/JabRef/jabref/blob/main/CONTRIBUTING.md#pull-request-process](CONTRIBUTING.md) for details.
8
+
- jobName: windows installer and portable version
9
+
message: >
10
+
Your code does not compile.
11
+
Please ensure your changes compile successfully before pushing changes.
12
+
13
+
14
+
To verify compilation locally, run `./gradlew build` or try running JabRef.
15
+
- jobName: 'Conflicts with target branch'
16
+
message: >
17
+
Your pull request conflicts with the target branch.
18
+
19
+
20
+
Please [merge `upstream/main`](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-branch-from-the-command-line) with your code.
21
+
For a step-by-step guide to resolve merge conflicts, see <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line>.
1
22
- jobName: Checkstyle
2
23
message: >
3
24
Your code currently does not meet [JabRef's code guidelines](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-13-code-style.html).
@@ -37,22 +58,13 @@
37
58
message: |
38
59
While the PR was in progress, a new version of JabRef has been released.
39
60
You have to merge `upstream/main` and move your entry in `CHANGELOG.md` up to the section `## [Unreleased]`.
40
-
- jobName: 'Unit tests'
41
-
message: >
42
-
JUnit tests are failing.
43
-
In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details".
44
-
This brings you to the test output.
45
-
46
-
47
-
You can then run these tests in IntelliJ to reproduce the failing tests locally.
48
-
We offer a quick test running howto in the section [Final build system checks](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-12-build.html#final-build-system-checks) in our setup guide.
49
61
- jobName: no-force-push
50
62
message: >
51
63
Do not force-push!
52
64
Force pushing is a very bad practice when working together on a project (mainly because it is [not supported well by GitHub itself](https://github.com/orgs/community/discussions/3478)).
53
65
Commits are lost and comments on commits lose their context, thus making it harder to review changes.
54
66
At the end, all commits will be [squashed](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits) anyway before being merged into the `main` branch.
55
-
- jobName: 'Mark issue as in progress'
67
+
- jobName: 'Determine issue number'
56
68
message: |
57
69
Your pull request needs to link an issue.
58
70
@@ -84,11 +96,18 @@
84
96
- ✅ `Fixes https://github.com/JabRef/jabref/issues/xyz` links pull-request to issue. Merging the PR will close the issue.
85
97
- ✅ `Fixes https://github.com/Koppor/jabref/issues/xyz` links pull-request to issue. Merging the PR will close the issue.
86
98
- ❌ `Fixes [#xyz](https://github.com/JabRef/jabref/issues/xyz)` links pull-request to issue. Merging the PR will **NOT** close the issue.
87
-
- jobName: 'Conflicts with target branch'
99
+
- jobName: 'Submodules not modified'
88
100
message: >
89
-
Your pull request conflicts with the target branch.
101
+
Your pull request modified git submodules.
90
102
91
103
92
-
Please merge `upstream/main` with your code.
93
-
Preferrably, do this using `git` in your machine:
94
-
Conflicts in `CHANGELOG.md` will be handled by a union of changes.
104
+
Please follow our [FAQ on submodules](https://devdocs.jabref.org/code-howtos/faq.html#submodules) to fix.
105
+
- jobName: 'Unit tests'
106
+
message: >
107
+
JUnit tests are failing.
108
+
In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details".
109
+
This brings you to the test output.
110
+
111
+
112
+
You can then run these tests in IntelliJ to reproduce the failing tests locally.
113
+
We offer a quick test running howto in the section [Final build system checks](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-12-build.html#final-build-system-checks) in our setup guide.
👋 Hey @{{ handle }}, thank you for your interest in this issue! 🎉
@@ -29,7 +29,7 @@ jobs:
29
29
30
30
Happy coding! 🚀
31
31
32
-
⏳ Please note, you will be automatically unassigned if the issue isn't closed within **{{ total_days }} days** (by **{{ unassigned_date }}**). A maintainer can also add the "**{{ pin_label }}**" label to prevent automatic unassignment.
32
+
⏳ Please note, you will be automatically unassigned if there is not a (draft) pull request within **{{ total_days }} days** (by **{{ unassigned_date }}**).
33
33
assignment_suggestion_comment: >
34
34
👋 Hey @{{ handle }}, looks like you’re eager to work on this issue—great! 🎉
35
35
It also looks like you skipped reading our [CONTRIBUTING.md](https://github.com/JabRef/jabref/blob/main/CONTRIBUTING.md), which explains exactly how to participate. No worries, it happens to the best of us.
0 commit comments