Conversation
* feat: auto-create GitHub repo on first sandbox creation When POST /api/sandboxes creates a sandbox for an account without a GitHub repo, automatically creates a private repo in the recoupable org and clones it into the sandbox. Returns github_repo in response. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: move GitHub repo setup to background Trigger.dev task Replace synchronous ensureGithubRepo call in POST /api/sandboxes with fire-and-forget triggerSetupSandbox. This lets the endpoint return the sandboxId faster while repo creation happens in a background task. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: remove triggerSetupSandbox from POST handler GitHub repo setup now happens entirely via defense-in-depth in runSandboxCommandTask's ensureGithubRepo call. Remove the fire-and-forget trigger from the POST handler and its associated tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: remove dead API-side github/sandbox files These files are no longer imported anywhere — repo setup now lives entirely in Recoup-Tasks. Removed: - lib/github/ensureGithubRepo.ts - lib/github/cloneRepoIntoSandbox.ts - lib/github/createGithubRepo.ts - lib/supabase/account_snapshots/updateAccountSnapshotGithubRepo.ts - lib/trigger/triggerSetupSandbox.ts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: trigger setup-sandbox task on sandbox creation Wire up triggerSetupSandbox in createSandboxPostHandler so every new sandbox fires the setup-sandbox Trigger.dev task (creates GitHub repo, clones, snapshots). Fire-and-forget with graceful error handling. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * revert: remove createSandbox response restructuring and dead code Revert the SandboxCreateResult wrapper (sandbox + response) back to the original flat SandboxCreatedResponse return. Delete unused sanitizeRepoName. These changes are unrelated to the setup-sandbox trigger goal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor: use single runId field in sandbox response When a command is provided, runId is the command task ID. When no command, runId is the setup task ID. Removes setupRunId for a consistent response shape. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
|
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 |
Routine merge of test branch into main.