Move from issue templates to issue forms

[vedarolap]

Summary

• Ports bug_report.md, feature_request.md, and submit-an-egg-idea.md to GitHub issue forms, keeping the same fields/content
• Adds config.yml linking to Discussions and the ROOST Discord server, and disabling blank issues (maintainers can still file them directly)
• Mirrors the structure roostorg/coop already adopted in roostorg/coop#674, which this issue points to as the reference

Closes #335

Test plan

• Validated all new .yml files parse as valid YAML
• Preview each form's rendering via GitHub's issue-form preview (only visible once merged/on GitHub)

Summary by CodeRabbit

• Documentation

  • Added structured issue forms for bug reports, feature requests, and new ideas.
  • Added required prompts and checklists to improve the quality and completeness of submissions.
  • Added contact links for discussions and contributor chat.

• Chores

  • Disabled blank issue creation.
  • Removed older Markdown-based issue templates in favor of the new structured forms.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b303c36d-e8c1-417b-9ffa-e7304b0bb89f

📥 Commits

Reviewing files that changed from the base of the PR and between 958900a and a00df77.

📒 Files selected for processing (7)

• .github/ISSUE_TEMPLATE/bug.yml
• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/config.yml
• .github/ISSUE_TEMPLATE/egg-idea.yml
• .github/ISSUE_TEMPLATE/feature.yml
• .github/ISSUE_TEMPLATE/feature_request.md
• .github/ISSUE_TEMPLATE/submit-an-egg-idea.md

💤 Files with no reviewable changes (3)

• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/feature_request.md
• .github/ISSUE_TEMPLATE/submit-an-egg-idea.md

---

📝 Walkthrough

Walkthrough

The repository now uses structured GitHub issue forms for bug reports, feature requests, and Egg ideas. Blank issue creation is disabled, contact links are configured, and the previous Markdown templates are removed.

Changes

Issue intake

Layer / File(s)	Summary
Issue intake routing .github/ISSUE_TEMPLATE/config.yml	Disables blank issues and adds contact links for GitHub Discussions and Discord.
Bug report form .github/ISSUE_TEMPLATE/bug.yml, .github/ISSUE_TEMPLATE/bug_report.md	Adds required bug-report fields, optional environment and diagnostic fields, and a Code of Conduct checklist while removing the Markdown template.
Feature and idea forms .github/ISSUE_TEMPLATE/feature.yml, .github/ISSUE_TEMPLATE/feature_request.md, .github/ISSUE_TEMPLATE/egg-idea.yml, .github/ISSUE_TEMPLATE/submit-an-egg-idea.md	Adds structured forms for feature requests and Egg ideas while removing their Markdown templates.

Estimated code review effort: 2 (Simple) | ~10 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 summarizes the main change: migrating repository issue templates to GitHub issue forms.
Linked Issues check	✅ Passed	The PR matches #335 by converting the existing markdown issue templates into structured GitHub issue forms.
Out of Scope Changes check	✅ Passed	All shown changes support the template-to-form migration and related issue-template configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[julietshen]

Nice, thank you so much for this contribution!

[julietshen]

Thanks again for this one! Quick curiosity question, unrelated to merging, are these contributions coming through an AI agent/pipeline? No issue either way, just want to understand the pattern so we can update our AGENTS.md/CONTRIBUTING guidance if it'd be useful for future agent-authored PRs.