Add default GitHub issue template#195
Merged
Merged
Conversation
- Add a GitHub issue template for feature, fix, and scoped change requests - Prompt for summary, rationale, current behavior, expected behavior, and scope notes
Contributor
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 19 minutes and 28 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA new GitHub issue template was added to standardize issue submissions with predefined YAML configuration and Markdown sections for feature requests, bug reports, and scoped changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/ISSUE_TEMPLATE/default.md (1)
15-22: Optional: add “Reproduction steps” and “Environment” prompts for bug reports.This can improve first-pass debugging quality without changing the template’s intent.
Suggested template extension
## Current behavior What happens today? +## Reproduction steps +How can we reproduce it? + +## Environment +OS, runtime/toolchain version, and relevant dependency versions. + ## Expected behavior What should happen instead?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/ISSUE_TEMPLATE/default.md around lines 15 - 22, Update the issue template to include two optional prompts for bug reports: add a "Reproduction steps" section and an "Environment" section adjacent to the existing headings (e.g., near "## Current behavior", "## Expected behavior", or "## Scope notes") so reporters can provide steps to reproduce and runtime details (OS, browser, versions, config) without changing intent; ensure the new headings are clearly labeled as optional and placed logically within the template to improve first-pass debugging.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/ISSUE_TEMPLATE/default.md:
- Around line 15-22: Update the issue template to include two optional prompts
for bug reports: add a "Reproduction steps" section and an "Environment" section
adjacent to the existing headings (e.g., near "## Current behavior", "##
Expected behavior", or "## Scope notes") so reporters can provide steps to
reproduce and runtime details (OS, browser, versions, config) without changing
intent; ensure the new headings are clearly labeled as optional and placed
logically within the template to improve first-pass debugging.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9a037b0c-3e68-44bd-b5c8-dff7f637f7fb
📒 Files selected for processing (1)
.github/ISSUE_TEMPLATE/default.md
- Add guidance to include repro steps and environment details for bugs
Contributor
Suite Timing
Measured on ubuntu-latest x64. |
Contributor
Benchmark Results274 benchmarks Interpreted: 🟢 138 improved · 🔴 100 regressed · 36 unchanged · avg +1.5% arraybuffer.js — Interp: 🟢 13, 1 unch. · avg +9.1% · Bytecode: 🔴 14 · avg -10.2%
arrays.js — Interp: 🟢 19 · avg +7.0% · Bytecode: 🔴 19 · avg -10.1%
async-await.js — Interp: 🟢 6 · avg +7.0% · Bytecode: 🔴 6 · avg -9.4%
classes.js — Interp: 🟢 31 · avg +8.2% · Bytecode: 🔴 24, 7 unch. · avg -10.5%
closures.js — Interp: 🟢 10, 1 unch. · avg +4.2% · Bytecode: 🔴 11 · avg -10.8%
collections.js — Interp: 🟢 7, 5 unch. · avg +2.9% · Bytecode: 🔴 11, 1 unch. · avg -5.9%
destructuring.js — Interp: 🟢 16, 🔴 2, 4 unch. · avg +3.0% · Bytecode: 🔴 22 · avg -10.2%
fibonacci.js — Interp: 🟢 5, 🔴 2, 1 unch. · avg +1.3% · Bytecode: 🔴 8 · avg -11.5%
for-of.js — Interp: 🔴 7 · avg -3.0% · Bytecode: 🔴 7 · avg -9.3%
helpers/bench-module.js — Interp: 0 · Bytecode: 0
iterators.js — Interp: 🔴 18, 2 unch. · avg -3.7% · Bytecode: 🔴 20 · avg -11.1%
json.js — Interp: 🟢 14, 🔴 1, 5 unch. · avg +2.7% · Bytecode: 🔴 20 · avg -8.1%
jsx.jsx — Interp: 🟢 2, 🔴 10, 9 unch. · avg -1.4% · Bytecode: 🔴 21 · avg -5.0%
modules.js — Interp: 🔴 8, 1 unch. · avg -5.0% · Bytecode: 🔴 9 · avg -9.2%
numbers.js — Interp: 🟢 6, 🔴 3, 2 unch. · avg +1.2% · Bytecode: 🔴 11 · avg -10.9%
objects.js — Interp: 🟢 1, 🔴 6 · avg -3.0% · Bytecode: 🟢 2, 🔴 4, 1 unch. · avg -3.3%
promises.js — Interp: 🔴 12 · avg -6.1% · Bytecode: 🔴 12 · avg -8.6%
regexp.js — Interp: 🟢 2, 🔴 8, 1 unch. · avg -2.8% · Bytecode: 🔴 10, 1 unch. · avg -7.8%
strings.js — Interp: 🔴 9, 2 unch. · avg -4.5% · Bytecode: 🟢 1, 🔴 10 · avg -8.1%
typed-arrays.js — Interp: 🟢 6, 🔴 14, 2 unch. · avg -0.7% · Bytecode: 🔴 22 · avg -11.0%
Measured on ubuntu-latest x64. Benchmark ranges compare cached main-branch min/max ops/sec with the PR run; overlapping ranges are treated as unchanged noise. Percentage deltas are secondary context. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/ISSUE_TEMPLATE/default.md.Testing
Summary by CodeRabbit