Repository navigation
0.7.12: big imports finish with gild clone - #9
Merged
Merged
Conversation
…d clone; importing the same source again picks up the waiting job. 0.7.12
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An import too large for gild's servers (over 500 MB) is now marked
local: truein 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 duringgild clone, then clones as usual. Re-runninggild repo importfor 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 typecheck0;npm test23/23 (the message test now assertsgild clone sami/linux).-claude