[orc] branch master updated: ORC-651: Use GitHub Pull Request Template

[do...@apache.org]

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

dongjoon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/orc.git


The following commit(s) were added to refs/heads/master by this push:
     new ead6ca4  ORC-651: Use GitHub Pull Request Template
ead6ca4 is described below

commit ead6ca4780a184e39e132c1cfa83706108554975
Author: Dongjoon Hyun <do...@apache.org>
AuthorDate: Sun Aug 2 11:45:10 2020 -0700

    ORC-651: Use GitHub Pull Request Template
    
    ### What changes were proposed in this pull request?
    
    This PR aims to add `GitHub Pull Request Template`.
    
    ### Why are the changes needed?
    
    This will help contributors and reviewers to provide a standardized way to communicate.
    
    ### How was this patch tested?
    
    Manually review the template.
    
    Closes #525
---
 .github/PULL_REQUEST_TEMPLATE | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
new file mode 100644
index 0000000..01c8d0a
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -0,0 +1,32 @@
+<!--
+Thanks for sending a pull request!  Here are some tips for you:
+  1. File a JIRA issue first and use it as a prefix of your PR title, e.g., `ORC-001: Fix ABC`.
+  2. Use your PR title to summarize what this PR proposes instead of describing the problem.
+  3. Make PR title and description complete because these will be the permanent commit log.
+  4. If possible, provide a concise and reproducible example to reproduce the issue for a faster review.
+  5. If the PR is unfinished, use GitHub PR Draft feature.
+-->
+
+### What changes were proposed in this pull request?
+<!--
+Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
+If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
+  1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
+  2. If there is a discussion in the mailing list, please add the link.
+-->
+
+
+### Why are the changes needed?
+<!--
+Please clarify why the changes are needed. For instance,
+  1. If you propose a new API, clarify the use case for a new API.
+  2. If you fix a bug, you can clarify why it is a bug.
+-->
+
+
+### How was this patch tested?
+<!--
+If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
+If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
+If tests were not added, please describe why they were not added and/or why it was difficult to add.
+-->