Resolve paths when blaming files #4357
Open
+4
−3
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
bruntib
approved these changes
Nov 21, 2024
|
@tomhughes Thanks for the patch. Could you, please, force-push a dummy change, so the test workflow is triggered? For some reason they don't start. Thank you! |
Both `git check-ignore` and `git blame` will error if run on a symbolic link, so resolve the path before running them.
tomhughes
force-pushed
the
blame-realpath
branch
from
e69d9cc
to
97abac1
Compare
|
I've forced a run now - there is one failure but it doesn't look related. |
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.
Both
git check-ignoreandgit blamewill error if run on a symbolic link, so resolve the path before running them.