This is an automated email from the ASF dual-hosted git repository.
jeffreyvo pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
The following commit(s) were added to refs/heads/main by this push:
new c2bd7d91bf minor: Add comment blocks to PR template (#8994)
c2bd7d91bf is described below
commit c2bd7d91bfb9e835daff07e41f194c0d3e53d858
Author: Jeffrey Vo <[email protected]>
AuthorDate: Tue Dec 16 10:58:43 2025 +0900
minor: Add comment blocks to PR template (#8994)
So they don't show up by default on rendered view.
---
.github/pull_request_template.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 49b34c6137..c2d07f49ab 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,28 +1,38 @@
# 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.
+-->
- Closes #NNN.
# 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.
+-->
# 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 these changes tested?
+<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
+-->
# 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 call them out.
+-->
