✨ Add user-story-template to issue templates#187
Conversation
|
Warning Review limit reached
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: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA new GitHub Issue Forms template file is added at ChangesIssue Template Addition
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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/user-story.yaml:
- Line 53: The placeholder value in the user-story YAML is being parsed as
invalid YAML because it contains an unquoted colon with a space. Update the
placeholder entry under the affected form field in the user-story template so
the entire value is quoted, using the existing placeholder key and surrounding
context to locate it. This will keep the literal example text intact and prevent
GitHub from treating it as a mapping.
🪄 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: CHILL
Plan: Pro
Run ID: 6cd33626-e6e9-4a68-93ca-5d6406e47c50
📒 Files selected for processing (1)
.github/ISSUE_TEMPLATE/user-story.yaml
There was a problem hiding this comment.
@Friedinger @Ruby11235 what are your thoughts about this
2 participants
This pull request introduces a new issue template for user stories to standardize and improve the process of submitting feature requests. The template guides users to provide clear user stories, acceptance criteria, and relevant context, while ensuring issues are not duplicates and that contributors agree to the project's Code of Conduct.
New Issue Template for User Stories:
.github/ISSUE_TEMPLATE/user-story.yamlto provide a structured form for submitting user stories, including sections for the user story description, acceptance criteria, definition of done, additional context, and required confirmations for duplicate checking and Code of Conduct agreement.