This is an automated email from the ASF dual-hosted git repository. khmarbaise pushed a commit to branch BADGES in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git
commit 887bb389fec65f4a66e243ce7b235c447c24d8e5 Author: Karl Heinz Marbaise <[email protected]> AuthorDate: Sat Jan 27 13:35:03 2018 +0100 Fixed typo plus reduced checking cause it's done by CI --- .github/pull_request_template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index d1f09bc..c04497b 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -8,10 +8,10 @@ contribution quickly and easily: - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MENFORCER-XXX` with the appropriate JIRA issue. Best practice - is to use the JIRA issue title in the pull reqeust title and in the first line of the + is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - - [ ] Run `mvn -Prun-its clean verify` to make sure basic checks pass. A more thorough check will + - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. If your pull request is about ~20 lines of code you don't need to sign an -- To stop receiving notification emails like this one, please contact [email protected].
