fix(issue-templates): add default labels to issue templates

[msranjana]

Description

Summary

This PR adds default labels to the GitHub issue templates so that newly created issues are automatically categorized.

Closes #534

Problem

The existing issue templates did not define a top-level labels field. As a result, issues created from the templates were opened without any labels, requiring maintainers to manually categorize every new issue.

Changes Made

Added the following default labels to the issue templates:

• .github/ISSUE_TEMPLATE/bug_report.yml

  • Added labels: ["bug"]

• .github/ISSUE_TEMPLATE/feature_request.yml

  • Added labels: ["enhancement"]

• .github/ISSUE_TEMPLATE/integration_request.yml

  • Added labels: ["enhancement"]

Why This Change?

Automatically applying labels when an issue is created:

• Reduces manual triage work for maintainers.
• Ensures bugs and feature requests are categorized consistently.
• Improves issue organization and filtering from the moment an issue is opened.

Files Changed

• .github/ISSUE_TEMPLATE/bug_report.yml
• .github/ISSUE_TEMPLATE/feature_request.yml
• .github/ISSUE_TEMPLATE/integration_request.yml

Verification

Verified the following:

• Opened each issue template from the New issue page.

• Confirmed the expected default label appears on the issue draft:

  • Bug Report → bug
  • Feature Request → enhancement
  • Integration Request → enhancement

Fixes #534

---

Checklist

• I have run pnpm lint and all checks pass
• I have run pnpm typecheck and there are no TypeScript errors
• I have run pnpm build and all packages build successfully
• I have run pnpm test and all tests pass
• No tests were required for this configuration-only change
• No documentation updates were required

Screenshots / Demos (if applicable)

N/A. This change only updates GitHub issue template configuration.

Additional Notes

This is a configuration-only change that improves the issue creation workflow by automatically assigning the appropriate default labels to new issues.

Summary by CodeRabbit

Chores

• Bug reports are now automatically labeled as bugs when submitted.
• Feature requests and integration requests are automatically labeled as enhancements.
• Duplicate-search links for integration requests now use the enhancement label for more consistent issue tracking.

[vercel]

@msranjana is attempting to deploy a commit to the corsair Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

Adds automatic categorization to GitHub issue forms.

• Applies the bug label to bug reports.
• Applies the enhancement label to feature and integration requests.

Confidence Score: 5/5

The PR appears safe to merge with no actionable issues identified.

The changes add correctly placed static label arrays to the three GitHub issue forms without altering their fields or validation behavior.

Important Files Changed

Filename	Overview
.github/ISSUE_TEMPLATE/bug_report.yml	Adds the valid top-level bug default label to the bug-report issue form.
.github/ISSUE_TEMPLATE/feature_request.yml	Adds the valid top-level enhancement default label to the feature-request issue form.
.github/ISSUE_TEMPLATE/integration_request.yml	Adds the valid top-level enhancement default label to the integration-request issue form.

_{Reviews (1): Last reviewed commit: "fix(issue-templates): add default labels..." | Re-trigger Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 90cef37d-9c93-43a3-8ff9-ee8793755a5b

📥 Commits

Reviewing files that changed from the base of the PR and between 9190322 and d60924d.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/bug_report.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/ISSUE_TEMPLATE/bug_report.yml

---

📝 Walkthrough

Walkthrough

The three GitHub issue templates now assign default labels. Integration duplicate-search links now use the enhancement label.

Changes

Issue template labels

Layer / File(s)	Summary
Add default issue labels .github/ISSUE_TEMPLATE/*	The bug report template assigns bug. The feature request and integration request templates assign enhancement. Integration duplicate-search links now query enhancement.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the primary change: adding default labels to issue templates.
Linked Issues check	✅ Passed	The three templates receive the labels required by issue #534: bug or enhancement.
Out of Scope Changes check	✅ Passed	All changes support issue #534, including updating duplicate-search links to match the new enhancement label.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[Dhirenderchoudhary]

LGTM

[ambikeesshh]

auto-labels are fine now
thanks!