This is an automated email from the ASF dual-hosted git repository.
jark pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss-benchmarks.git
The following commit(s) were added to refs/heads/main by this push:
new 9248d98 [github] Add GitHub pull request template
9248d98 is described below
commit 9248d98027ecd0e51190994ef58a1f5749b828a2
Author: Jark Wu <[email protected]>
AuthorDate: Tue Aug 5 11:17:47 2025 +0800
[github] Add GitHub pull request template
---
.github/PULL_REQUEST_TEMPLATE.md | 41 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..39a0d1b
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,41 @@
+<!--
+*Thank you very much for contributing to Fluss - we are happy that you want to
help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
+
+## Contribution Checklist
+
+ - Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss-benchmarks/issues). Exceptions are made
for typos in JavaDoc or documentation files, which need no issue.
+
+ - Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
+
+ - Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
+
+ - Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
+
+ - Each pull request should address only one issue, not mix up code from
multiple issues.
+
+
+**(The sections below can be removed for hotfixes or typos)**
+-->
+
+### Purpose
+
+<!-- Linking this pull request to the issue -->
+Linked issue: close #xxx
+
+<!-- What is the purpose of the change -->
+
+### Brief change log
+
+<!-- Please describe the changes made in this pull request and explain how
they address the issue -->
+
+### Tests
+
+<!-- List UT and IT cases to verify this change -->
+
+### API and Format
+
+<!-- Does this change affect API or storage format -->
+
+### Documentation
+
+<!-- Does this change introduce a new feature -->
