andygrove opened a new pull request, #325:
URL: https://github.com/apache/datafusion-spark/pull/325
## Which issue does this PR close?
Part of #56: the "Pull request template, and issue templates with a field
for Spark versions" item.
## Rationale for this change
The repository has no pull request or issue templates. So new issues often
leave out the Spark version and Spark's result, which are needed to judge
whether `datafusion-spark` is wrong. New PRs don't say which Spark versions the
expected results were checked against.
## What changes are included in this PR?
- **`.github/pull_request_template.md`**: the same sections as
apache/datafusion's template, which PRs here already use. The guidance is
changed in two places:
- The testing section asks which Spark versions the expected results were
checked against, and how (the PySpark runner, the Spark source, or golden
files).
- The user-facing section points to the versioning policy in
`dev/release/README.md` for breaking API changes, instead of an `api change`
label, which this repository doesn't have.
- **`.github/ISSUE_TEMPLATE/bug_report.yml`**: required fields for the bug,
a query that reproduces it, and Spark's result (with a reminder to say whether
ANSI mode was on). There is also a required **Spark versions** field, and
optional fields for the `datafusion-spark` version and other context.
- **`.github/ISSUE_TEMPLATE/function_request.yml`**: a new template for the
most common kind of issue here, "Implement Spark-compatible `<function>`". It
has the sections the existing function issues use: what the function does,
examples, edge cases to test, and differences across Spark versions.
- **`.github/ISSUE_TEMPLATE/feature_request.yml`**: apache/datafusion's
feature request template, for anything that isn't a new function.
The issue templates use the existing `bug` and `enhancement` labels and the
`Bug` and `Feature` issue types, as apache/datafusion's do.
## Are these changes tested?
The issue templates are valid YAML. GitHub reports errors in an issue form
on the repository's "New issue" page once it is on `main`. Every file has the
SPDX header the license check requires.
## Are there any user-facing changes?
No.
_This PR was written by an LLM (Claude) and reviewed before opening._
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]