This is an automated email from the ASF dual-hosted git repository. viirya pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/spark-connect-gateway.git
commit 4a77c4ec21e8222d735c683c724984e10df9b244 Author: Liang-Chi Hsieh <[email protected]> AuthorDate: Tue Aug 11 13:10:12 2026 -0700 Add pull request template Reuse the standard Apache Spark PR template (What changes / Why / user-facing change / How tested / Generative AI tooling), matching apache/spark-connect-rust. Co-authored-by: Claude Code --- .github/PULL_REQUEST_TEMPLATE | 54 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE new file mode 100644 index 0000000..af7bbe2 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE @@ -0,0 +1,54 @@ +<!-- +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 you refactor some codes with changing classes, showing the class hierarchy will help reviewers. + 2. If you fix some SQL features, you can provide some references of other DBMSes. + 3. If there is design documentation, please add the link. + 4. 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 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. +--> + + +### Does this PR introduce _any_ user-facing change? +<!-- +Note that it means *any* user-facing change including all aspects such as new features, bug fixes, or other behavior changes. Documentation-only updates are not considered user-facing changes. + +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. +--> + + +### Was this patch authored or co-authored using generative AI tooling? +<!-- +If generative AI tooling has been used in the process of authoring this patch, please include the +phrase: 'Generated-by: ' followed by the name of the tool and its version. +If no, write 'No'. +Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details. +--> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
