Skip to content

Commit f6d03f6

Browse files
hgschmieslachiewicz
authored andcommitted
Remove superflous whitespace from PR template
It keeps driving me nuts.
1 parent c22c8fe commit f6d03f6

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

.github/pull_request_template.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
1-
Following this checklist to help us incorporate your
1+
Following this checklist to help us incorporate your
22
contribution quickly and easily:
33

4-
- [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed
5-
for the change (usually before you start working on it). Trivial changes like typos do not
6-
require a JIRA issue. Your pull request should address just this issue, without
4+
- [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed
5+
for the change (usually before you start working on it). Trivial changes like typos do not
6+
require a JIRA issue. Your pull request should address just this issue, without
77
pulling in other changes.
88
- [ ] Each commit in the pull request should have a meaningful subject line and body.
99
- [ ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`,
1010
where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice
11-
is to use the JIRA issue title in the pull request title and in the first line of the
11+
is to use the JIRA issue title in the pull request title and in the first line of the
1212
commit message.
1313
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
14-
- [ ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will
14+
- [ ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will
1515
be performed on your pull request automatically.
1616

1717
If your pull request is about ~20 lines of code you don't need to sign an
1818
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
1919
please ask on the developers list.
2020

21-
To make clear that you license your contribution under
21+
To make clear that you license your contribution under
2222
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
2323
you have to acknowledge this by using the following check-box.
2424

0 commit comments

Comments
 (0)