chore: modernize GitHub issue templates - #1556
Conversation
Replace the outdated issue templates with GitHub issue forms (YAML) that reflect this repo hosting @prisma/studio-core (Prisma CLI v7+, embedded distributions, and the VS Code extension): - bug_report.yml: required fields for Studio distribution, database + version, Prisma/studio-core versions, OS/browser, repro steps, expected vs actual behavior, plus optional logs - feature_request.yml: problem, proposed solution, alternatives - config.yml: disable blank issues (spam mitigation) and add contact links for prisma/prisma issues, Discord, and docs Closes #1391 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughAdds GitHub issue templates for bug reports and feature requests, with required and optional structured fields and automatic labels. Configures issue creation to disable blank issues and provides contact links for Prisma ORM/CLI issues, Discord support, and documentation. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
|
Compute preview deployed. Branch: |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. You're currently rate limited under our Fair Usage Limits Policy. Your recent PR review activity is in the 95th percentile or higher among CodeRabbit users, so adaptive limits apply. Your next review will be available in 33 minutes. |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Warning
CodeRabbit couldn't request changes on this pull request because it doesn't have sufficient GitHub permissions.
Please grant CodeRabbit Pull requests: Read and write permission and re-run the review.
Actionable comments posted: 3
🤖 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.yml:
- Around line 106-112: Update the Logs field in the bug report template,
identified by its label and description, to instruct reporters to redact
connection strings, tokens, API keys, and personal data before sharing logs
publicly. Keep the existing requests for browser, terminal, and VS Code output
unchanged.
- Around line 50-62: Remove the prefilled value from the required versions
textarea identified by id “versions” so template comments cannot satisfy
validation. Use a placeholder for the Prisma and optional studio-core version
guidance, or leave the field empty while preserving the required validation.
In @.github/ISSUE_TEMPLATE/config.yml:
- Around line 6-8: Align the question-routing guidance between README.md and the
issue template entry for “Prisma Discord.” Update the conflicting README
instructions or remove/adjust the Discord contact option so integration
questions consistently follow one documented route.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: f190fa42-b6a8-41d0-91ee-af79863a1eb4
📒 Files selected for processing (3)
.github/ISSUE_TEMPLATE/bug_report.yml.github/ISSUE_TEMPLATE/config.yml.github/ISSUE_TEMPLATE/feature_request.yml
- bug_report.yml: use placeholder + render instead of value prefill so required fields cannot be satisfied by untouched template text - bug_report.yml: add secret-redaction guidance to the logs field - config.yml/README.md: align questions policy — Discord for general usage questions, GitHub issues for integration/API questions about embedding @prisma/studio-core Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
Fixes #1391
The repo currently has no
.github/ISSUE_TEMPLATEat all on main, and spam/empty issues are a recurring problem. This adds modern GitHub issue forms:kind/bug): required Studio distribution dropdown (CLIprisma studio/ embedded@prisma/studio-core/ VS Code extension), database + version, Prisma & studio-core versions, OS/browser, repro steps, expected vs actual; optional logs. Redirects ORM/CLI problems to prisma/prisma and warns against including database credentials.kind/feature): problem, proposed solution, optional alternatives.blank_issues_enabled: false(spam mitigation) + contact links to prisma/prisma issues, the Prisma Discord, and the docs.Tone and structure mirror prisma/prisma's issue forms, substantially leaner. No changeset — no package change.
🤖 Generated with Claude Code