chore(github): add discussion templates and route the issue chooser

[imshashank]

Discussions has been enabled on this repository with six categories, zero posts and no templates. The issue chooser pointed at the Discussions root, so somebody arriving with a question landed on an empty tab with no prompt to answer.

What this changes

Three discussion templates, in .github/DISCUSSION_TEMPLATE/:

• Ideas asks what is painful and what you do instead, rather than what widget you want. It states the three permanently off-the-table things up front, matching feature_request.yml, so nobody writes a long post about billing.
• Q&A points at the documentation first, asks for the goal rather than only the stuck step, and asks for full error output. It also says plainly not to post security problems there.
• Show and tell asks what got in the way, which is the part worth reading.

The tone follows the existing issue templates rather than inventing a second voice.

The issue chooser now links three specific destinations instead of one generic one: the contribution map, Q&A, and Ideas. The old "Question or idea" link sent both audiences to the same place and neither found what they needed.

Why now

Part of the Community and repo health milestone, specifically #221.

Checks

bun run check-comments covers YAML and passes. No source files touched, so lint, typecheck and tests are unaffected.

🤖 Generated with Claude Code

Greptile Summary

Adds structured GitHub Discussion templates and routes issue-chooser visitors to more specific community destinations.

• Adds Ideas, Q&A, and Show and Tell discussion forms.
• Adds explicit sensitive-output redaction guidance to the Q&A form.
• Replaces the generic Discussions link with contribution, Q&A, and Ideas links.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; the previously reported disclosure concern is addressed by explicit guidance to redact sensitive output.

Important Files Changed

Filename	Overview
.github/DISCUSSION_TEMPLATE/ideas.yml	Adds a structured form for discussing workflow problems, workarounds, possible solutions, and prior art.
.github/DISCUSSION_TEMPLATE/q-a.yml	Adds a Q&A form with documentation and security-reporting directions; the follow-up wording fully addresses the prior sensitive-output disclosure concern.
.github/DISCUSSION_TEMPLATE/show-and-tell.yml	Adds a showcase form covering implementation details, links, and encountered friction.
.github/ISSUE_TEMPLATE/config.yml	Replaces the generic Discussions destination with direct contribution, Q&A, and Ideas links.

_{Reviews (3): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
orbit	Ready	Preview	Aug 8, 2026 1:05pm

[coderabbitai]

Warning

Review limit reached

@imshashank, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ad377436-276a-4195-87b3-c551d84782eb

📥 Commits

Reviewing files that changed from the base of the PR and between 8f5d79b and 113dc3c.

📒 Files selected for processing (4)

• .github/DISCUSSION_TEMPLATE/ideas.yml
• .github/DISCUSSION_TEMPLATE/q-a.yml
• .github/DISCUSSION_TEMPLATE/show-and-tell.yml
• .github/ISSUE_TEMPLATE/config.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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