This is an automated email from the ASF dual-hosted git repository.
yikun pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark-docker.git
The following commit(s) were added to refs/heads/master by this push:
new 30fd82f [SPARK-40757][INFRA] Add PULL_REQUEST_TEMPLATE for
spark-docker
30fd82f is described below
commit 30fd82f313c4ecd44f4181e6a4cf2e1d9463c628
Author: Yikun Jiang <yikunk...@gmail.com>
AuthorDate: Wed Oct 12 10:47:31 2022 +0800
[SPARK-40757][INFRA] Add PULL_REQUEST_TEMPLATE for spark-docker
### What changes were proposed in this pull request?
Initialize with
https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE and
remove some unsued note
### Why are the changes needed?
Add PULL_REQUEST_TEMPLATE for `spark-docker`
### Does this PR introduce _any_ user-facing change?
No, dev only
### How was this patch tested?
New PR after this merged
Closes #8 from Yikun/SPARK-40757.
Authored-by: Yikun Jiang <yikunk...@gmail.com>
Signed-off-by: Yikun Jiang <yikunk...@gmail.com>
---
.github/PULL_REQUEST_TEMPLATE | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
new file mode 100644
index 0000000..5268131
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -0,0 +1,41 @@
+<!--
+Thanks for sending a pull request! Here are some tips for you:
+ 1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
+ 2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
+ 3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
+ 4. Be sure to keep the PR description updated to reflect all changes.
+ 5. Please write your PR title to summarize what this PR proposes.
+ 6. If possible, provide a concise example to reproduce the issue for a
faster review.
+-->
+
+### 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 there is design documentation, please add the link.
+ 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 fix a bug, you can clarify why it is a bug.
+-->
+
+
+### Does this PR introduce _any_ user-facing change?
+<!--
+Note that it means *any* user-facing change including all aspects such as the
documentation fix.
+If yes, please clarify the previous behavior and the change this PR proposes -
provide the console output, description and/or an example to show the behavior
difference if possible.
+If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
+If no, write 'No'.
+-->
+
+
+### 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.
+-->
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org
