Repository navigation
chore: Add contributor sentiment to contribute - #6688
Merged
Merged
Conversation
coderfender
approved these changes
Oct 5, 2026
Contributor
Author
|
Thanks @coderfender |
mohitgurav20
pushed a commit
to mohitgurav20/datafusion
that referenced
this pull request
Oct 8, 2026
…pache#26120) ## Which issue does this PR close? - No tracking issue, this is a small repository chore. ## Rationale for this change Ports apache/datafusion-comet#6688, which took the idea from the [iceberg-rust issue templates](https://github.com/apache/iceberg-rust/tree/main/.github/ISSUE_TEMPLATE). Reporters say up front whether they can contribute the fix or feature, so reviewers don't have to ask in a follow-up comment. ## What changes are included in this PR? Adds an optional "Willingness to contribute" dropdown with three options to `bug_report.yml` and `feature_request.yml`. The wording is specific to bug fixes in the bug template and to features in the feature template. ## What is the testing strategy for this PR? Issue templates have no automated tests. Both files parse as YAML and the dropdown has the same shape as in the iceberg-rust and Comet templates. ## Are there any user-facing changes? New issues filed from the bug report and feature request forms get one extra optional dropdown. There are no API changes.
Omega359
pushed a commit
to Omega359/arrow-datafusion
that referenced
this pull request
Oct 11, 2026
…pache#26120) ## Which issue does this PR close? - No tracking issue, this is a small repository chore. ## Rationale for this change Ports apache/datafusion-comet#6688, which took the idea from the [iceberg-rust issue templates](https://github.com/apache/iceberg-rust/tree/main/.github/ISSUE_TEMPLATE). Reporters say up front whether they can contribute the fix or feature, so reviewers don't have to ask in a follow-up comment. ## What changes are included in this PR? Adds an optional "Willingness to contribute" dropdown with three options to `bug_report.yml` and `feature_request.yml`. The wording is specific to bug fixes in the bug template and to features in the feature template. ## What is the testing strategy for this PR? Issue templates have no automated tests. Both files parse as YAML and the dropdown has the same shape as in the iceberg-rust and Comet templates. ## Are there any user-facing changes? New issues filed from the bug report and feature request forms get one extra optional dropdown. There are no API changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
The idea was taken from https://github.com/apache/iceberg-rust/tree/main/.github/ISSUE_TEMPLATE and I personally find it very useful rather than asking contributors that filing tickets, if they ready to contribute
What changes are included in this PR?
How are these changes tested?