Conversation
Deletes the GitHub repo and snapshot record for an account. Supports API key and Bearer auth with optional account_id for org keys. GitHub repo deletion is best-effort — snapshot is always deleted. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Don't delete the snapshot record if the GitHub repo can't be deleted, otherwise we lose the repo reference with no way to clean it up later. Co-Authored-By: Claude Opus 4.6 <[email protected]>
If the repo doesn't exist on GitHub (already deleted or never created), proceed with snapshot cleanup instead of aborting. Co-Authored-By: Claude Opus 4.6 <[email protected]>
When no github_repo is stored in the snapshot (or no snapshot exists), falls back to searching the recoupable GitHub org for repos whose name contains the account ID. Ensures robust cleanup even if the snapshot record was previously deleted. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Logs the full error response from GitHub API to help diagnose 403 errors. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
…ete-apisandboxes feat: add DELETE /api/sandboxes endpoint
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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. ✨ 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 |
1 participant
Summary
🤖 Generated with Claude Code