consolidating the bug reports to one issue template

[Shrividya]

Motivation for this PR is the conversation in the following links:

• https://lists.apache.org/thread/jgsc8j92qwo4fqnvxbn5op97qrpk328v
• https://cwiki.apache.org/confluence/display/AIRFLOW/GitHub+Issues+Restructure+Proposal shared by @shahar1

Changes include:

• Consolidation of multiple issue type under one issue template with defined categories and values( as per applicability).
• Removal of redundant fields across the multiple templates.
• Doc issue template removed
• file name updates across precommit yamls and prek/check_airflow_bug_report_template.py accordingly

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[bugraoz93]

Look good to me! It follows the proposed approach in the docs. Thanks for the PR!

[shahar1]

Looks good! Got a few comments, please take a look on you have the time.
Thanks!

[potiuk]

@Shrividya This PR has a few issues that need to be addressed before it can be reviewed — please see our Pull Request quality criteria.

Issues found:

• ⚠️ Unresolved review comments: This PR has 3 unresolved review threads from maintainers: @shahar1 (MEMBER): 3 unresolved threads. Please review and resolve all inline review comments before requesting another review. You can resolve a conversation by clicking 'Resolve conversation' on each thread after addressing the feedback. See pull request guidelines.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Shrividya]

@shahar1 all the comments have been addressed, would you mind reviewing again so that the comments can be marked as resolved or if it needs further changes?

[shahar1]

Overall LGTM, I'd rather have at least one more review by committer for merging.
Great job!

[Copilot]

Pull request overview

This PR consolidates multiple GitHub issue templates into a single Airflow issue report form, updates CI/pre-commit checks to point at the new template, and removes now-redundant templates.

Changes:

• Consolidated core/providers/Helm/Task SDK bug reporting into .github/ISSUE_TEMPLATE/1-airflow_bug_report.yml with a new category dropdown.
• Removed separate Providers / Helm chart / Docs issue templates and introduced a maintainer-only “Task and Meta” free-form template.
• Updated the pre-commit hook and its checker script to validate the provider list in the consolidated template.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
scripts/ci/prek/check_airflow_bug_report_template.py	Points validation at the new consolidated issue template
.pre-commit-config.yaml	Updates the pre-commit hook to run against the new template
.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml	Consolidates issue reporting, adds category/provider/Helm fields
.github/ISSUE_TEMPLATE/3-free_form.yml	Adds maintainer-only meta/task issue form
.github/ISSUE_TEMPLATE/3-airflow_providers_bug_report.yml	Removed (replaced by consolidated template)
.github/ISSUE_TEMPLATE/4-airflow_helmchart_bug_report.yml	Removed (replaced by consolidated template)
.github/ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml	Removed

[Pyasma]

thanks for the PR :)

[potiuk]

NICE!

[github-actions]

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 3b6ee39 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.