You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker and confirmed that I was unable to find existing issues for the feature I am requesting.
The feature request
Add in GitHub Desktop’s Options a configuration to select a custom path/command to a git executable, with a blank default be git as queried from the OS’s PATH.
WSLgit can be achieved with a separate toggle switch or simply with the command wsl git entered into the config above.
Proposed solution
GitHub Desktop then uses users’ choice of git executables and follows their global configs
Assuming GitHub Desktop currently fetches its bundled git through the OS PATH, this customizability instead means the user doesn’t need to verify and possibly tinker with their PATH.
– which is actually a challenge for users of WSL git
This is a feature request split from the above referenced (inäctive) bug report 12431. There, @fluffynuts compared the bundled git.exe with Git’s official portable git.exe and mentioned this possibility of overriding the bundled git.exe with a customized path-to-executable.
Similarly, I have WSL Ubuntu and I use the Ubuntu git occasionally.
Options popup, Git tab: (Taken from the documentation repo)
The text was updated successfully, but these errors were encountered:
Related: I just tried adding my GPG key from WSL GPG. But of course, GitHub Desktop is a Windows app and so uses Windows GPG only. Guess I’ll have to regenerate the key? EDIT: Naw, looks like I can import keys
Search for existing feature requests
The feature request
Add in GitHub Desktop’s Options a configuration to select a custom path/command to a
git
executable, with a blank default begit
as queried from the OS’s PATH.git
can be achieved with a separate toggle switch or simply with the commandwsl git
entered into the config above.Proposed solution
git
executables and follows their global configsgit
as queried from the OS’s PATH?git
through the OS PATH, this customizability instead means the user doesn’t need to verify and possibly tinker with their PATH.git
git
hooksAdditional context
git.exe
with Git’s official portablegit.exe
and mentioned this possibility of overriding the bundledgit.exe
with a customized path-to-executable.git
occasionally.Options popup, Git tab: (Taken from the documentation repo)
The text was updated successfully, but these errors were encountered: