Disable extensions.worktreeConfig when disabling sparse-checkout
#1692
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
cory-miller
approved these changes
Apr 23, 2024
This was referenced Apr 23, 2024
|
When do you plan to release this? I just wonder if we should wait for fix or just pin to old version 🙌 |
|
@huv1k We have created release |
1 task
This was referenced Dec 31, 2024
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 we released v4.1.3, there were reports that it interfered with some third party tools.
see the following issues:
It turns out that calling
git sparse-checkout disablehas a side effect. It places the local repo clone in worktree mode, albeit with only a single "tree".This fix neutralizes that side effect by explicitly disabling worktree mode.