[arrow-rs] branch nevi-me-patch-1 created (now 4e61130)

[ne...@apache.org]

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

nevime pushed a change to branch nevi-me-patch-1
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git.


      at 4e61130  Update PR template by commenting out instructions

This branch includes the following new commits:

     new 4e61130  Update PR template by commenting out instructions

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[arrow-rs] 01/01: Update PR template by commenting out instructions

[ne...@apache.org]

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

nevime pushed a commit to branch nevi-me-patch-1
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git

commit 4e6113026a186aff92ff304af5faffceefa1cdd4
Author: Wakahisa <ne...@gmail.com>
AuthorDate: Mon May 10 18:35:27 2021 +0200

    Update PR template by commenting out instructions
    
    Some contributors don't remove the guidelines when creating PRs, so it might be more convenient if we hide them behind comments.
    The comments are still visible when editing, but are not displayed when the markdown is rendered
---
 .github/pull_request_template.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 5da0d08..95403e1 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,19 +1,31 @@
 # Which issue does this PR close?
 
+<!---
 We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123.
+-->
 
 Closes #.
 
  # Rationale for this change
+ 
+ <!---
  Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
- Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.  
+ Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.
+-->
 
 # What changes are included in this PR?
 
+<!---
 There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR.
+-->
 
 # Are there any user-facing changes?
 
+
+<!---
 If there are user-facing changes then we may require documentation to be updated before approving the PR.
+-->
 
+<!---
 If there are any breaking changes to public APIs, please add the `breaking change` label.
+-->