-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve check list #5587
Merged
Merged
Improve check list #5587
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,20 @@ | ||
<!-- describe the changes you have made here: what, why, ... | ||
Link issues by using the following pattern: [#333](https://github.com/JabRef/jabref/issues/333) or [koppor#49](https://github.com/koppor/jabref/issues/47). | ||
The title of the PR must not reference an issue, because GitHub does not support autolinking there. --> | ||
<!-- | ||
Describe the changes you have made here: what, why, ... | ||
Link issues by using the following pattern: #333. | ||
If you fixed a koppor issue, link it with following pattern: [koppor#47](https://github.com/koppor/jabref/issues/47). | ||
The title of the PR must not reference an issue, because GitHub does not support autolinking there. | ||
--> | ||
|
||
## Checklist | ||
|
||
---- | ||
<!-- | ||
- All items with `[ ]` are still a TODO. | ||
- All items checked with `[x]` are done. | ||
- Remove item not applicable | ||
--> | ||
|
||
- [ ] Change in CHANGELOG.md described | ||
- [ ] Tests created for changes | ||
- [ ] Manually tested changed features in running JabRef | ||
- [ ] Change in CHANGELOG.md described (if applicable) | ||
- [ ] Tests created for changes (if applicable) | ||
- [ ] Manually tested changed features in running JabRef (always required) | ||
- [ ] Screenshots added in PR description (for bigger UI changes) | ||
- [ ] [Checked documentation](https://docs.jabref.org/): Is the information available and up to date? If not: Issue created at <https://github.com/JabRef/user-documentation/issues>. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The body of the PR is always the most important one, thus I don't like the heading here as it puts too much emphasize on something relatively unimportant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted the thing to be more intuitively separated. Using
--
it always felt a bit off. I wondered whether we should add a section## Description