fix: backup cache

[yxtay]

No description provided.

[coderabbitai]

Warning

Review limit reached

@yxtay, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: baca79e8-26a7-41b8-9a56-5a3e85d309cd

📥 Commits

Reviewing files that changed from the base of the PR and between 06ac10a and 1f6fb3f.

📒 Files selected for processing (3)

• backup/resticprofile/profiles.yaml
• sync/rsync/exclude.txt
• unison/common.prf

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/backup-cache

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Code Review

This pull request updates exclusion patterns across restic, rsync, and Unison configurations to ignore *-cache and logs directories. The review feedback highlights opportunities to improve consistency across these tool configurations by ensuring that *-tmp, logs, and *-logs patterns are uniformly excluded across all three systems.

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.

[gemini-code-assist]

To maintain consistency with the Unison ignore patterns (which now ignore *-tmp via brace expansion), we should also exclude *-tmp from the restic backups.

        - "*-cache"
        - "*-tmp"

[gemini-code-assist]

To ensure consistency across all backup and sync configurations, we should also exclude *-tmp/**, logs/**, and *-logs/** patterns from rsync. This prevents temporary files and logs from being unnecessarily synchronized.

*-cache/**
*-tmp/**
logs/**
*-logs/**

[gemini-code-assist]

Since logs has been excluded from restic backups, we should also exclude it from Unison synchronization. We can elegantly achieve this by adding logs to the brace expansion pattern, which will automatically ignore logs, *.logs, and *-logs.

ignore = Name {,*.,*-}{cache,tmp,logs}