fix: backup cache#238
Conversation
|
Warning Review limit reached
Next review available in: 2 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 Plus Run ID: 📒 Files selected for processing (2)
✨ 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 |
There was a problem hiding this comment.
Code Review
This pull request updates the exclude patterns in both resticprofile and rsync configurations to target files and directories ending with .cache instead of just .cache. Feedback was provided on the rsync exclude pattern, pointing out that *.cache/** only excludes directory contents and suggesting *.cache instead to correctly exclude both files and directories.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| cache/** | ||
| *-cache/** | ||
| .cache/** | ||
| *.cache/** |
There was a problem hiding this comment.
Using *.cache/** only excludes the contents of directories ending with .cache. It does not exclude files ending with .cache (e.g., config.cache), nor does it exclude the directory itself (which leaves empty .cache directories on the destination). To exclude both files and directories ending with .cache (including their contents), use *.cache instead.
*.cache
No description provided.