Conversation
|
Warning Review limit reached
Next review available in: 57 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. 📝 WalkthroughWalkthroughWhitespace and indentation were normalized across ChangesJSON Whitespace Reformatting
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
![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
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (6)
data/ko/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/ko/tutorials.json` around lines 1 - 18, The file data/ko/tutorials.json has formatting that does not comply with the project's formatting standards, as indicated by the CI lint failure. Run the project's code formatter on this file to automatically reformat it according to the project's whitespace and style conventions. This will ensure the file passes the Actions/Lint CI checks.Source: Pipeline failures
data/pt/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/pt/tutorials.json` around lines 1 - 18, The file data/pt/tutorials.json has formatting that does not match the project's formatter standards and is causing CI lint checks to fail. Run the project's formatter tool on this file to automatically apply the correct whitespace and formatting conventions. This will ensure the file passes the Actions / Lint check before the pull request can be merged.Source: Pipeline failures
data/sr/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/sr/tutorials.json` around lines 1 - 18, The tutorials.json file has whitespace formatting that does not comply with the project's formatter standards and is causing the Lint CI check to fail. Run the project's formatter on the data/sr/tutorials.json file to apply the correct formatting, ensuring the file passes the linting checks before merging.Source: Pipeline failures
data/tr/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/tr/tutorials.json` around lines 1 - 18, The file data/tr/tutorials.json has formatting that does not match the project's code style standards and is causing the linting check to fail. Run the project's configured formatter (check the project configuration for the formatter tool being used, such as prettier or similar) on this file to automatically reformat the whitespace and indentation to comply with the project standards. Once formatted, the file should pass the Actions / Lint CI check.Source: Pipeline failures
data/it/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/it/tutorials.json` around lines 1 - 18, The tutorials.json file has whitespace formatting that does not match the project's formatter standards, causing the Lint CI check to fail. Run the project's code formatter on the data/it/tutorials.json file to automatically reformat the JSON with the correct indentation and spacing according to project standards. This will resolve the CI Lint action failure.Source: Pipeline failures
data/pl/tutorials.json (1)
1-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winReformat this file with the project formatter.
CI already reports this file would be rewritten, so the current whitespace still fails
Actions / Lint. Please apply the formatter output before merging.🤖 Prompt for 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. In `@data/pl/tutorials.json` around lines 1 - 18, The tutorials.json file contains improperly formatted JSON that is failing the lint checks. The file has entries with fields like regex, name, and url that need to be reformatted according to the project's formatter standards. Run the project's formatter tool on the tutorials.json file to automatically fix the whitespace and formatting issues, ensuring it passes the CI linting checks before merging.Source: Pipeline failures
🤖 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 `@data/ko/arcanes.json`:
- Around line 2-460: The arcanes.json file is not formatted according to the
repository's expected formatting standards, which is causing the CI lint check
to fail. Run the repository's JSON formatter tool on the data/ko/arcanes.json
file to ensure the whitespace, indentation, and overall formatting matches the
repository's configuration exactly. This must be done before the changes will
pass CI validation.
---
Outside diff comments:
In `@data/it/tutorials.json`:
- Around line 1-18: The tutorials.json file has whitespace formatting that does
not match the project's formatter standards, causing the Lint CI check to fail.
Run the project's code formatter on the data/it/tutorials.json file to
automatically reformat the JSON with the correct indentation and spacing
according to project standards. This will resolve the CI Lint action failure.
In `@data/ko/tutorials.json`:
- Around line 1-18: The file data/ko/tutorials.json has formatting that does not
comply with the project's formatting standards, as indicated by the CI lint
failure. Run the project's code formatter on this file to automatically reformat
it according to the project's whitespace and style conventions. This will ensure
the file passes the Actions/Lint CI checks.
In `@data/pl/tutorials.json`:
- Around line 1-18: The tutorials.json file contains improperly formatted JSON
that is failing the lint checks. The file has entries with fields like regex,
name, and url that need to be reformatted according to the project's formatter
standards. Run the project's formatter tool on the tutorials.json file to
automatically fix the whitespace and formatting issues, ensuring it passes the
CI linting checks before merging.
In `@data/pt/tutorials.json`:
- Around line 1-18: The file data/pt/tutorials.json has formatting that does not
match the project's formatter standards and is causing CI lint checks to fail.
Run the project's formatter tool on this file to automatically apply the correct
whitespace and formatting conventions. This will ensure the file passes the
Actions / Lint check before the pull request can be merged.
In `@data/sr/tutorials.json`:
- Around line 1-18: The tutorials.json file has whitespace formatting that does
not comply with the project's formatter standards and is causing the Lint CI
check to fail. Run the project's formatter on the data/sr/tutorials.json file to
apply the correct formatting, ensuring the file passes the linting checks before
merging.
In `@data/tr/tutorials.json`:
- Around line 1-18: The file data/tr/tutorials.json has formatting that does not
match the project's code style standards and is causing the linting check to
fail. Run the project's configured formatter (check the project configuration
for the formatter tool being used, such as prettier or similar) on this file to
automatically reformat the whitespace and indentation to comply with the project
standards. Once formatted, the file should pass the Actions / Lint CI check.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 2d7a2093-1148-4699-957f-4e714c862d5f
📒 Files selected for processing (14)
data/cs/arcanes.jsondata/cs/tutorials.jsondata/it/arcanes.jsondata/it/tutorials.jsondata/ko/arcanes.jsondata/ko/tutorials.jsondata/pl/arcanes.jsondata/pl/tutorials.jsondata/pt/arcanes.jsondata/pt/tutorials.jsondata/sr/arcanes.jsondata/sr/tutorials.jsondata/tr/arcanes.jsondata/tr/tutorials.json
|
Tick the box to add this pull request to the merge queue (same as
|
|
🎉 This PR is included in version 3.16.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
2 participants
Summary by CodeRabbit
regex,name,effect,rarity,location,thumbnail,info, andurl).