ci: per-run mktemp staging dir in deploy (fixes scp permission denied) - #6
Conversation
A fixed staging path (/tmp/planner-deploy) is owned by whichever OS Login user created it first. When a manual deploy (a human account) ran before CI, the github-deployer service account could not write into it and scp failed with "permission denied". Use a fresh `mktemp -d` per run — always owned by the deploying user — and remove it afterward. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016aitZGthghNeJEdjYFsZT8
|
Warning Review limit reached
Next review available in: 39 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
3 participants
The first CI deploy (run #31631803047) failed scp with permission denied: the fixed
/tmp/planner-deploywas owned by a prior manual-deploy user, sogithub-deployercouldn't write into it. Switch to a per-runmktemp -d(always owned by the deploying user), clean it up after. Pipeline itself already verified green after clearing the stale dir. 🤖 Generated with Claude Code