Skip to content

Update templates to use forms#872

Open
Rycochet wants to merge 2 commits into
mainfrom
chore/update-templates
Open

Update templates to use forms#872
Rycochet wants to merge 2 commits into
mainfrom
chore/update-templates

Conversation

@Rycochet
Copy link
Copy Markdown
Collaborator

@Rycochet Rycochet commented May 15, 2026

Make use of github forms, these could probably be improved, but it's a good start.

Summary by CodeRabbit

  • Chores
    • Replaced legacy issue templates with structured, form-style templates for bug reports and feature requests
    • Disabled blank issues and added quick-access links to community support and docs during issue submission
    • Improved submission guidance with required fields and a human-verification checkbox to streamline reports and requests

Review Change Stack

@dosubot dosubot Bot added the size:M This PR changes 30-99 lines, ignoring generated files. label May 15, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

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: 92902b6b-9694-448a-a99d-e3b2b85d4924

📥 Commits

Reviewing files that changed from the base of the PR and between 19adedd and bfbbd2d.

📒 Files selected for processing (1)
  • .github/ISSUE_TEMPLATE/bug_report.yaml
✅ Files skipped from review due to trivial changes (1)
  • .github/ISSUE_TEMPLATE/bug_report.yaml

📝 Walkthrough

Walkthrough

Issue templates are migrated from Markdown to YAML form schemas. A config file disables blank issues and adds Discord/docs contact links. New YAML templates for bug reports and feature requests add metadata, structured fields, typed inputs, and required human-written confirmation checkboxes.

Changes

Issue Template Modernization

Layer / File(s) Summary
Template configuration and contact links
.github/ISSUE_TEMPLATE/config.yaml
GitHub issue behavior set to disallow blank issues and contact links for Discord community support and documentation are added.
Structured bug and feature report forms
.github/ISSUE_TEMPLATE/bug_report.yaml, .github/ISSUE_TEMPLATE/feature_request.yaml
Bug report and feature request templates replaced with YAML issue forms including metadata, required/optional fields, typed inputs (OS, browser, version), and a required human-written confirmation checkbox.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through templates, tidy and bright,
Fields lined in YAML, each one just right.
No blank reports sneaking in under night,
Discord and docs ready — a comforting sight.
🥕✨

🚥 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 'Update templates to use forms' clearly and concisely describes the main change: migrating GitHub issue templates from markdown to structured form format.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-templates

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/ISSUE_TEMPLATE/bug_report.yaml:
- Line 2: The description field in the bug report template currently says
"Create a report to help us improve Lingarr"—rename the project mention to
"Tinyauth" by updating the description value so it reads something like "Create
a report to help us improve Tinyauth"; adjust only the project name in the
existing 'description' YAML key to correct the copy-paste error.
- Around line 59-82: The YAML template has inconsistent indentation for the
attributes under several input fields (ids: os, browser, tinyauth, docker);
normalize the indentation for the nested keys (label and placeholder) to match
the rest of the template (use 4-space indentation for attributes' children),
ensuring the attributes block for each input id follows the same indentation
level and style as other input fields in the file.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 980fb9c9-832f-434e-9430-aafd408f809d

📥 Commits

Reviewing files that changed from the base of the PR and between ca06099 and 19adedd.

📒 Files selected for processing (5)
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/bug_report.yaml
  • .github/ISSUE_TEMPLATE/config.yaml
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/ISSUE_TEMPLATE/feature_request.yaml
💤 Files with no reviewable changes (2)
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/feature_request.md

Comment thread .github/ISSUE_TEMPLATE/bug_report.yaml Outdated
Comment thread .github/ISSUE_TEMPLATE/bug_report.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant