Repository navigation
fix: only treat a missing branch as a new branch on clone (0.9) - #71
Merged
EdmondDantes21 merged 1 commit intoOct 15, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Clone(network blip, 5xx, rate limit) is treated as "branch does not exist": the existing branch is checked out as an orphan,RemoveGlob("*")empties it, and the next commit deletes every target file not in the template.GetLatestCommitRemotewrapsErrBranchNotFound, andClonereturns any other error so the reconcile retries.TestCloneFailsOnTransientBranchLookupError(git HTTP server that fails the first request; fails without the fix) andTestGetLatestCommitRemoteBranchNotFound.🤖 Generated with Claude Code