Skip to content

Conversation

@dscho
Copy link
Contributor

@dscho dscho commented Jun 16, 2022

This addresses the issue raised in #5031.

/cc @chrisd8088

@dscho dscho requested a review from a team as a code owner June 16, 2022 21:30
Copy link
Member

@chrisd8088 chrisd8088 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this! I had one comment so far, and I'll give it a try later on a fresh Windows VM (once I remember how to tinker with the installer again!)

Copy link
Member

@chrisd8088 chrisd8088 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've run a first test and found one thing I think needs to be resolved -- let me know if you agree.

It was reported in git-lfs#5031
that Git LFS' installer aborts because it does not find the `git`
executable when Git for Windows was installed with the "Bash Only" PATH
option, i.e. in the mode where `PATH` is not modified at all.

Detect this situation, and fall back to implicitly extend the `PATH` to
find Git for Windows' `git.exe`.

Co-authored-by: Chris Darroch <[email protected]>
Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho force-pushed the handle-BashOnly-Git-for-Windows-gracefully branch from d1b1edb to 865d6ee Compare June 22, 2022 09:01
Copy link
Member

@chrisd8088 chrisd8088 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great and works as expected on my test VM -- thank you! 🙇

@chrisd8088 chrisd8088 merged commit 5521dc1 into git-lfs:main Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants