fix(nlab-api): fetch target branches outside configured refspecs - #111
Merged
Merged
Conversation
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.
Repositories cloned with
--single-branchcould report an existing target branch as missing because fetchingoriginhonored the restricted fetch refspec. Creating a tracking branch also failed when the requested branch was outside that refspec.Fetch the requested branch into its explicit remote-tracking ref and create the local branch with
--no-track. Existing explicit fast-forward pulls continue to update it. Preserve the repository's fetch configuration and existing worktree protections. The shared repository path covers initialization, generation, and Discover.Validation: