This is an automated email from the ASF dual-hosted git repository.
csy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/auron.git
The following commit(s) were added to refs/heads/master by this push:
new 39113880 [AURON #1722] Use PR title and description for commit message
(#1723)
39113880 is described below
commit 391138801dac988344a3625297ac21e969f91f6a
Author: cxzl25 <[email protected]>
AuthorDate: Thu Dec 11 13:52:04 2025 +0800
[AURON #1722] Use PR title and description for commit message (#1723)
---
.asf.yaml | 1 +
.github/pull_request_template.md | 32 ++------------------------------
2 files changed, 3 insertions(+), 30 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index dff4bf68..532cc595 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -24,5 +24,6 @@ github:
- arrow
enabled_merge_buttons:
squash: true
+ squash_commit_message: PR_TITLE_AND_DESC
merge: false
rebase: false
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index c9b2022b..53a84152 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,42 +1,14 @@
<!--
-Thanks for sending a pull request! Please keep the following tips in mind:
- Start the PR title with the related issue ID, e.g. '[AURON #XXXX] Short
summary...'.
- - Make your PR title clear and descriptive, summarizing what this PR changes.
- - Provide a concise example to reproduce the issue, if possible.
- - Keep the PR description up to date with all changes.
-->
-
# 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 #.
+Closes #<issue_number>
- # 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.
--->
+# Rationale for this change
# 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 `api change`
label.
--->
# 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.
--->
