Conversation
|
Warning Rate limit exceeded
⌛ 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. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (16)
📝 WalkthroughWalkthroughAdds a CI linting step that installs R, runs a new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/scripts/check_style.R (1)
6-10: Consider listing files that need styling.The current message tells users to run
styler::style_pkg()but doesn't indicate which files need changes. Printing the affected file names would help developers identify and fix specific issues faster.♻️ Proposed improvement to list affected files
if (any(files$changed)) { + changed_files <- files$file[files$changed] + message("The following files need styling:") + message(paste(" -", changed_files, collapse = "\n")) + message("") message("The following files need styling. Please run:") message(" styler::style_pkg(transformers = styler::tidyverse_style(indent_by = 4))") quit(status = 1) }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/scripts/check_style.R around lines 6 - 10, The current block checking if (any(files$changed)) prints generic guidance but not which files need styling; update the if block that uses files$changed to also list the affected file names (e.g., derive the file paths from the same files object and include them in the message before quitting) so the user can see exactly which files need styling when the script exits. Ensure you modify the messages in that conditional (the message(...) calls) to include the affected file list derived from files$changed.
🤖 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/scripts/check_style.R:
- Around line 6-10: The current block checking if (any(files$changed)) prints
generic guidance but not which files need styling; update the if block that uses
files$changed to also list the affected file names (e.g., derive the file paths
from the same files object and include them in the message before quitting) so
the user can see exactly which files need styling when the script exits. Ensure
you modify the messages in that conditional (the message(...) calls) to include
the affected file list derived from files$changed.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ee03db10-e027-42ed-8309-048cbc253334
📒 Files selected for processing (2)
.github/scripts/check_style.R.github/workflows/dry-run-build.yml
🚧 Files skipped from review as they are similar to previous changes (1)
- .github/workflows/dry-run-build.yml
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## devel #81 +/- ##
==========================================
+ Coverage 80.09% 80.44% +0.34%
==========================================
Files 7 7
Lines 839 900 +61
==========================================
+ Hits 672 724 +52
- Misses 167 176 +9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
Motivation and Context
Please include relevant motivation and context of the problem along with a short summary of the solution.
Changes
Please provide a detailed bullet point list of your changes.
Testing
Please describe any unit tests you added or modified to verify your changes.
Checklist Before Requesting a Review
Motivation and Context
This PR adds an automated, dry-run code style check to the repository's CI for PRs targeting devel. The goal is to detect deviations from the tidyverse style (with 4-space indentation) early in the review process without modifying files in the workflow run, prompting contributors to run styler locally before merge.
Detailed Changes
.github/workflows/dry-run-build.yml
.github/scripts/check_style.R
Unit Tests
Coding Guidelines