feat: repo.sh - shallow cloning still tracks remote branches. #140
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
When setting SHALLOW_CLONE=1 setting for the `make dev.clone` target, developers are left with clones which cannot checkout remote branches for development. They are forced to search stackoverflow and ask AI bots how to fix this problem and discover an obscure command to fix their local clone. This PR just captures that work so others don't suffer.
pwnage101
force-pushed
the
pwnage101/repo-script-shallow-clone-track-branches
branch
from
fd35d51 to
4acb0ba
Compare
brobro10000
approved these changes
May 14, 2025
adamstankiewicz
approved these changes
May 14, 2025
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.
When setting SHALLOW_CLONE=1 setting for the
make dev.clonetarget, developers are left with clones which cannot checkout remote branches for development. They are forced to search stackoverflow and ask AI bots how to fix this problem and discover an obscure command to fix their local clone.This PR just captures that work so others don't suffer.