(parquet-java) branch master updated: GH-2932: Adjust PR template to reference GitHub issue tracker (#2933)

[gangwu]

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

gangwu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/parquet-java.git


The following commit(s) were added to refs/heads/master by this push:
     new fb9c17458 GH-2932: Adjust PR template to reference GitHub issue 
tracker (#2933)
fb9c17458 is described below

commit fb9c1745808473f9fa6eb4bf3d03a4e2bab442e5
Author: Rok Mihevc <r...@mihevc.org>
AuthorDate: Mon Jun 24 16:33:39 2024 +0200

    GH-2932: Adjust PR template to reference GitHub issue tracker (#2933)
---
 .github/PULL_REQUEST_TEMPLATE.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 1a2ade407..99922564a 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,10 +1,10 @@
 Make sure you have checked _all_ steps below.
 
-### Jira
+### Issue
 
-- [ ] My PR addresses the following [Parquet 
Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references
-  them in the PR title. For example, "PARQUET-1234: My Parquet PR"
-    - https://issues.apache.org/jira/browse/PARQUET-XXX
+- [ ] My PR addresses the following [GitHub 
issues](https://github.com/apache/parquet-java/issues) and references
+  them in the PR title. For example, "GH-1234: My Parquet PR"
+    - https://github.com/apache/parquet-java/issues/1234
     - In case you are adding a dependency, check if the license complies with
       the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
 
@@ -14,10 +14,10 @@ Make sure you have checked _all_ steps below.
 
 ### Commits
 
-- [ ] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines
+- [ ] My commits all reference GitHub issues in their subject lines. In 
addition, my commits follow the guidelines
   from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
-    1. Subject is limited to 50 characters (not including Jira issue reference)
+    1. Subject is limited to 50 characters (not including GitHub issue 
reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters