Open
Conversation
📝 WalkthroughWalkthroughThe pull request adds an informational markdown note to the bug report issue template, outlining a policy for issues submitted without reproduction steps. The note includes instructions for reporters to delete it after reading. The modification is minimal and does not alter the template's structure or validation rules. Changes
Fun fact: Did you know that the term "bug" in software was inspired by an actual moth found in a computer in 1947? Admiral Grace Hopper's team discovered the insect in a Harvard Mark II computer, and it became the origin of the term "debugging"—making bug reports a tradition that dates back nearly 80 years! 🚥 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 |
@jsverse/transloco
@jsverse/transloco-locale
@jsverse/transloco-messageformat
@jsverse/transloco-optimize
@jsverse/transloco-persist-lang
@jsverse/transloco-persist-translations
@jsverse/transloco-preload-langs
@jsverse/transloco-schematics
@jsverse/transloco-scoped-libs
@jsverse/transloco-utils
@jsverse/transloco-validator
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/ISSUE_TEMPLATE/bug-report.yaml:
- Around line 6-10: The change was applied to the bug report issue template (the
YAML block with "type: markdown" and its value) but the PR description claims to
add "PR Checklist" and "PR Type" to a pull request template; confirm whether the
intent was to edit a PR template or the bug report; either update the PR
objectives to reflect that you're modifying the bug report note, or move/add the
new checklist/type controls to the actual PR template (create or edit the
repository's pull request template file such as PULL_REQUEST_TEMPLATE.md or
.github/pull_request_template) and remove or adjust the reproduction policy note
from the bug-report.yaml if it was unintended.
- Around line 6-10: The markdown block in the YAML issue template (the `type:
markdown` block under the `value:` key) includes an impossible-to-follow
instruction ("Please delete this note once you have read it") and a typo
("unreproducable"); remove the deletion instruction from that `value` text and
correct the typo to "unreproducible" (or "non-reproducible"), or alternatively
replace this YAML `type: markdown` block by moving the content to a `.md`
template if you need editable/deletable instructions; ensure the change targets
the `type: markdown` / `value:` content in the
.github/ISSUE_TEMPLATE/bug-report.yaml.
🪄 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: 30053692-d62c-486c-81f4-55784ea583ef
📒 Files selected for processing (1)
.github/ISSUE_TEMPLATE/bug-report.yaml
Comment on lines
+6
to
+10
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducable issues. Please delete this note once you have read it. | ||
|
|
There was a problem hiding this comment.
Inconsistency between PR objectives and actual changes.
The PR objectives describe adding "PR Checklist" and "PR Type" selection to a pull request template, but this file is a bug report issue template (.github/ISSUE_TEMPLATE/bug-report.yaml). The actual change adds a policy note about reproduction requirements to the issue template, which doesn't match the stated objectives.
Please verify:
- Is this the intended file for the changes described in the PR objectives?
- Should there be corresponding changes to a PR template file?
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/ISSUE_TEMPLATE/bug-report.yaml around lines 6 - 10, The change was
applied to the bug report issue template (the YAML block with "type: markdown"
and its value) but the PR description claims to add "PR Checklist" and "PR Type"
to a pull request template; confirm whether the intent was to edit a PR template
or the bug report; either update the PR objectives to reflect that you're
modifying the bug report note, or move/add the new checklist/type controls to
the actual PR template (create or edit the repository's pull request template
file such as PULL_REQUEST_TEMPLATE.md or .github/pull_request_template) and
remove or adjust the reproduction policy note from the bug-report.yaml if it was
unintended.
Instruction to delete the note is impossible in YAML form templates.
This is a YAML-based issue template that renders as a web form on GitHub. Markdown blocks (type: markdown) are displayed as static, read-only informational content—users cannot edit or delete them. The instruction "Please delete this note once you have read it" will confuse reporters since they have no way to comply.
Consider either:
- Removing the deletion instruction entirely
- Converting to a markdown-based template (
.md) if you need users to edit content
Also, there's a typo: "unreproducable" should be "unreproducible" (or "non-reproducible").
📝 Proposed fix
value: |
- > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducable issues. Please delete this note once you have read it.
+ > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducible issues.Fun i18n fact: The word "bug" translates to "böcek" in Turkish, "жук" (zhuk) in Russian, and "虫" (chóng) in Chinese—though in software contexts, many languages simply borrow the English word "bug" or use "error/defecto" instead! 🐛🌍
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/ISSUE_TEMPLATE/bug-report.yaml around lines 6 - 10, The markdown
block in the YAML issue template (the `type: markdown` block under the `value:`
key) includes an impossible-to-follow instruction ("Please delete this note once
you have read it") and a typo ("unreproducable"); remove the deletion
instruction from that `value` text and correct the typo to "unreproducible" (or
"non-reproducible"), or alternatively replace this YAML `type: markdown` block
by moving the content to a `.md` template if you need editable/deletable
instructions; ensure the change targets the `type: markdown` / `value:` content
in the .github/ISSUE_TEMPLATE/bug-report.yaml.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/ISSUE_TEMPLATE/bug-report.yaml">
<violation number="1" location=".github/ISSUE_TEMPLATE/bug-report.yaml:9">
P3: Fix the typo in the issue template notice (`unreproducable` → `unreproducible`).</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducable issues. Please delete this note once you have read it. |
There was a problem hiding this comment.
P3: Fix the typo in the issue template notice (unreproducable → unreproducible).
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/ISSUE_TEMPLATE/bug-report.yaml, line 9:
<comment>Fix the typo in the issue template notice (`unreproducable` → `unreproducible`).</comment>
<file context>
@@ -3,6 +3,11 @@ description: Report a bug in one of the Transloco packages
+ - type: markdown
+ attributes:
+ value: |
+ > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducable issues. Please delete this note once you have read it.
+
- type: checkboxes
</file context>
Suggested change
| > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducable issues. Please delete this note once you have read it. | |
| > **Note:** Our policy is that issues reported without a reproduction will be closed immediately and then reopened once a reproduction has been provided. Please respect the developers of this project by doing this. We give of our personal time to work on this project and would rather be spending our time fixing or enhancing the library than chasing down badly described or unreproducible issues. Please delete this note once you have read it. |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Summary by cubic
Add a note to the bug report issue template requiring a reproduction; reports without one will be closed and reopened once provided. This clarifies expectations and reduces time spent triaging unreproducible issues.
Written for commit a86ca53. Summary will update on new commits.
Summary by CodeRabbit
Chores