Skip to content

0.7.12: big imports finish with gild clone - #9

Merged
samifouad merged 1 commit into
mainfrom
claude/import-local-command
Oct 15, 2026
Merged

samifouad merged 1 commit into
mainfrom
claude/import-local-command

Conversation

@samifouad

Copy link
Copy Markdown
Member

An import too large for gild's servers (over 500 MB) is now marked local: true in its status, and its message reads "Too large to import on gild's servers (N GB). Import it from your machine: gild clone owner/name". gild CLI 0.6.18 runs the waiting import on the owner's machine during gild clone, then clones as usual. Re-running gild repo import for the same source picks up the waiting job instead of failing with "repository exists".

Contract: importStatus.local (optional boolean), mirrored in gildforge/cli.

Evidence: npm run typecheck 0; npm test 23/23 (the message test now asserts gild clone sami/linux).

-claude

…d clone; importing the same source again picks up the waiting job. 0.7.12
@samifouad
samifouad merged commit b9acc57 into main Oct 15, 2026
1 check passed
@samifouad
samifouad deleted the claude/import-local-command branch October 15, 2026 15:41

This branch was successfully deployed

1 active deployment
public-ci — 0c6344c7 Deployed Oct 15, 2026 by samifouad via check #34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant