[maven-compiler-plugin] branch master updated: Fix project key in PR template

[sl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new d2f9d77  Fix project key in PR template
d2f9d77 is described below

commit d2f9d77e1ce43597e2c314764dbfd9145d14fca8
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Sat Nov 13 09:46:44 2021 +0100

    Fix project key in PR template
---
 .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 bf9cc04..ec11d6f 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -6,8 +6,8 @@ contribution quickly and easily:
        require a JIRA issue.  Your pull request should address just this issue, without 
        pulling in other changes.
  - [ ] Each commit in the pull request should have a meaningful subject line and body.
- - [ ] Format the pull request title like `[MPH-XXX] - Fixes bug in ApproximateQuantiles`,
-       where you replace `MPH-XXX` with the appropriate JIRA issue. Best practice
+ - [ ] Format the pull request title like `[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles`,
+       where you replace `MCOMPILER-XXX` with the appropriate JIRA issue. Best practice
        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.