mirror of
https://github.com/stablyai/orca.git
synced 2026-11-15 18:37:24 +00:00
Neil
ac06c09040
Starting a cloud workspace from a GitHub repository with no clone here showed only a 'Starting <repo> in Orca Cloud…' toast. It now opens the same build sheet as a cloud create from a local clone: Start sandbox, Clone repository with git's progress, Open workspace; the same failure cards and JA-21b billing blocker (plan, hours, spend cap, payment; members get no See plans); Retry; and Back to draft (composer back on Orca Cloud with the GitHub repository picked and the prompt kept). Main: createFromGitHub runs the hosted driver's create path (createSandboxWithProgress, shared with the owned create): boot plan, create, waitForClone, with the same [orca-cloud] progress lines streamed on ephemeralVm:provisionEvent under the window's creation id, the same failure reason lines and codes (hostedCreateFailure), Cancel via ephemeralVm:cancelProvision, and an Idempotency-Key. The workspace id is fixed per creation so a Retry sends the same body. Renderer: the GitHub start is a pending creation with the Orca Cloud recipe and a githubSource; retryBackgroundWorktreeCreation routes it to its own runner. A Retry after a lost answer resends the same key (same sandbox back); after an answered failure it is a new attempt; after a failed open it only opens the sandbox it already has. The paired workspace has no environment-checks step.
11 lines
367 B
TypeScript
11 lines
367 B
TypeScript
/** What a GitHub-only Orca Cloud create starts from (D4, GH-CREATE-SHEET). */
|
|
export type GitHubCreateSource = {
|
|
repoUrl: string
|
|
/** `owner/repo`. */
|
|
fullName: string
|
|
/** The composer's text: the workspace's title and the agent's first prompt. */
|
|
prompt: string
|
|
/** The project the composer had selected, for Back to draft. */
|
|
composerRepoId: string
|
|
}
|