This is an automated email from the ASF dual-hosted git repository.
zhouky pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-celeborn.git
The following commit(s) were added to refs/heads/main by this push:
new 339d5854 [CELEBORN-134][INFRA] Enhance PULL_REQUEST_TEMPLATE (#1079)
339d5854 is described below
commit 339d5854698466a6b34248b2933fd153c3206598
Author: Cheng Pan <[email protected]>
AuthorDate: Wed Dec 14 10:07:56 2022 +0800
[CELEBORN-134][INFRA] Enhance PULL_REQUEST_TEMPLATE (#1079)
---
.github/PULL_REQUEST_TEMPLATE.md | 24 +++++++++---------------
1 file changed, 9 insertions(+), 15 deletions(-)
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index a172469d..56f83205 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,28 +1,22 @@
-# [BUG]/[FEATURE] title
+<!--
+Thanks for sending a pull request! Here are some tips for you:
+ - Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX] Your
PR title ...'.
+ - Be sure to keep the PR description updated to reflect all changes.
+ - Please write your PR title to summarize what this PR proposes.
+ - If possible, provide a concise example to reproduce the issue for a faster
review.
+-->
### What changes were proposed in this pull request?
-### 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.
--->
-
-### What are the items that need reviewer attention?
+### Why are the changes needed?
-### Related issues.
+### Does this PR introduce _any_ user-facing change?
-### Related pull requests.
### How was this patch tested?
-
-/cc @related-reviewer
-
-/assign @main-reviewer
