[maven-deploy-plugin] 02/02: Fix jira key in PR template

[sj...@apache.org]

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

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

commit 273179603fa8e4be751bace9c33b62abdac41037
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Fri Jan 20 20:46:58 2023 +0100

    Fix jira key in PR template
---
 .github/pull_request_template.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index b9b9dde..7f4ebfa 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,13 +1,13 @@
 Following this checklist to help us incorporate your 
 contribution quickly and easily:
 
- - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPH) filed 
+ - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEPLOY) filed 
        for the change (usually before you start working on it).  Trivial changes like typos do not 
        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 `[MDEPLOY-XXX] - Fixes bug in ApproximateQuantiles`,
+       where you replace `MDEPLOY-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.