Sort Git Tree Entries Correctly #2838
Merged
Conversation
This file contains 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
The Git tree entry sort oder is very particular. Tree entries are sorted as if tree entries (directories) had '/' appended to them. Git seems to rely on this order, causing errors if it is not followed.
justinsb
approved these changes
Feb 28, 2022
|
lgtm - this rings a bell! We should also check if there's a helper in go-git, maybe? |
|
I checked but the code is internal utility. |
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.
The Git tree entry sort oder is very particular. Tree entries are sorted
as if tree entries (directories) had '/' appended to them. Git seems to
rely on this order, causing errors if it is not followed.