Skip to content

chore: Add contributor sentiment to contribute - #6688

Merged
comphead merged 3 commits into
apache:mainfrom
comphead:chore
Oct 5, 2026
Merged

comphead merged 3 commits into
apache:mainfrom
comphead:chore

Conversation

@comphead

@comphead comphead commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

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?

@github-actions github-actions Bot added enhancement New feature or request area:ci CI/CD, GitHub Actions, build tooling labels Oct 5, 2026
@comphead

comphead commented Oct 5, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @coderfender

@comphead
comphead added this pull request to the merge queue Oct 5, 2026
Merged via the queue into apache:main with commit 38d941f Oct 5, 2026
22 checks passed
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:ci CI/CD, GitHub Actions, build tooling enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants