chore(docs): add GitHub Discussions ideas template

[KooshaPari]

User description

Summary

• Adds .github/DISCUSSION_TEMPLATE/ideas.yml (13 lines) — the only missing GitHub-hygiene template type after the issue-template pass.
• Complements existing ISSUE_TEMPLATE/bug_report.md and feature_request.md by providing a low-friction channel for open-ended idea discussions.
• Independent of open PRs chore(hygiene): add SUPPORT.md #46 and docs: add SUPPORT.md #47 (both add SUPPORT.md); no file overlap.

Test plan

• Verified only this file is added (no other changes).
• Branched from main; does not touch a8e9e43 or any other hygiene PR.
• File renders as a GitHub Discussions template picker entry under the ideas category.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only GitHub metadata; no application code or runtime behavior changes.

Overview
Adds .github/DISCUSSION_TEMPLATE/ideas.yml, a GitHub Discussions form template for the ideas category so contributors can open structured idea threads without filing a full feature issue.

The template pre-applies labels enhancement and discussion, titles threads with [Idea], and prompts for Problem, Proposed Direction, and Alternatives Considered—matching the hygiene pattern used for issue templates elsewhere in the repo.

^{Reviewed by Cursor Bugbot for commit 74f616a. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Add a GitHub Discussions template for ideas

What Changed

• Adds a new Discussions template for the ideas category so people can open structured idea threads
• New idea posts start with [Idea] and apply the enhancement and discussion labels automatically
• The template prompts contributors to include the problem, proposed direction, and alternatives considered

Impact

✅ Easier idea submissions
✅ More consistent discussion threads
✅ Clearer review of proposed changes

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request introduces a new GitHub Discussion template for ideas. The review feedback correctly points out that the template is missing the required 'name' and 'about' fields in its front matter, which are necessary for it to display properly in the template chooser UI, and provides a code suggestion to fix this.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

GitHub Discussion templates require name and about fields in the front matter to display correctly in the template chooser UI. Without these, the template may not be properly described or selectable by users.

---
name: Idea
about: Propose a new idea or feature direction
title: "[Idea] "
labels: ["enhancement", "discussion"]
category: ideas
---

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue.}

^{Reviewed by Cursor Bugbot for commit 74f616a. Configure here.}

[cursor]

Discussion template lacks required body

Medium Severity

The new ideas.yml follows issue-markdown frontmatter plus freeform sections, but GitHub discussion category forms require a top-level body array with at least one non-markdown input field. Without that schema, the Ideas picker may not load or may omit the intended structured prompts.

 

^{Reviewed by Cursor Bugbot for commit 74f616a. Configure here.}