This is an automated email from the ASF dual-hosted git repository.
andygrove pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion-java.git
The following commit(s) were added to refs/heads/main by this push:
new a651d31 docs: add GitHub issue and PR templates (#23)
a651d31 is described below
commit a651d31e9fcc222fb294c1963df0e4081e67a761
Author: Andy Grove <[email protected]>
AuthorDate: Wed May 13 07:33:16 2026 -0600
docs: add GitHub issue and PR templates (#23)
---
.github/ISSUE_TEMPLATE/bug_report.yml | 28 +++++++++++++++++++++
.github/ISSUE_TEMPLATE/feature_request.yml | 27 ++++++++++++++++++++
.github/pull_request_template.md | 40 ++++++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml
b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..ac5f082
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,28 @@
+name: Bug report
+description: Create a report to help us improve
+type: Bug
+labels: bug
+body:
+ - type: textarea
+ attributes:
+ label: Describe the bug
+ description: Describe the bug.
+ placeholder: >
+ A clear and concise description of what the bug is.
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: To Reproduce
+ placeholder: >
+ Steps to reproduce the behavior:
+ - type: textarea
+ attributes:
+ label: Expected behavior
+ placeholder: >
+ A clear and concise description of what you expected to happen.
+ - type: textarea
+ attributes:
+ label: Additional context
+ placeholder: >
+ Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml
b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 0000000..62449af
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,27 @@
+name: Feature request
+description: Suggest an idea for this project
+type: Feature
+labels: enhancement
+body:
+ - type: textarea
+ attributes:
+ label: Is your feature request related to a problem or challenge?
+ description: Please describe what you are trying to do.
+ placeholder: >
+ A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
+ (This section helps DataFusion developers understand the context and
*why* for this feature, in addition to the *what*)
+ - type: textarea
+ attributes:
+ label: Describe the solution you'd like
+ placeholder: >
+ A clear and concise description of what you want to happen.
+ - type: textarea
+ attributes:
+ label: Describe alternatives you've considered
+ placeholder: >
+ A clear and concise description of any alternative solutions or
features you've considered.
+ - type: textarea
+ attributes:
+ label: Additional context
+ placeholder: >
+ Add any other context or screenshots about the feature request here.
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..907d905
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,40 @@
+## 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 #.
+
+## 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.
+-->
+
+## 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 these changes tested?
+
+<!--
+We typically require tests for all PRs in order to:
+1. Prevent the code from being accidentally broken by subsequent changes
+2. Serve as another way to document the expected behavior of the code
+
+If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
+-->
+
+## 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.
+-->
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
