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
GitHub for Windows has always shipped with a complete git/bash command line environment. It's always been a big selling point, "the easiest way to get git running on your windows machine". We shared that user-facing environment with the app itself, shelling out for the stuff we couldn't do with libgit2. That has once or twice caused us problems when upgrading since the shell environment could break the ui.
Mac has also shipped with git but their environment has only been used internally by the app and hasn't been made publicly available. A long time ago there was a button in the app to install a command line environment but that was removed after Apple started shipping Git shims in 10.9.
Right now desktop ships with a slimmed down environment for both Mac and Windows which is only meant to be used internally. We need to figure out what we need to do as far as providing a shell environment for users on Windows.
Access to a command line environment is essential for things like conflicts where we currently need to tell the user to go resolve the conflicts themselves. GHfW default cop-out when we hit an unexpected error with git was to let the user launch the shell and figure it out from there (not saying I ever liked that).
Questions
How do we ship it? Exactly as we do today? 7-zip archive unpacked to magic dir and environment launched through GitHub.exe?
I know there was talk about a standalone shell thing a while back but I don't know how fleshed out that really was nor do I know if we have time to go for anything other than parity here.
I know this is something near and dear to @shiftkey's heart and I expect him to have a lot to say here, I'm only opening it so that we can start discussing it.
GitHub for Windows has always shipped with a complete git/bash command line environment. It's always been a big selling point, "the easiest way to get git running on your windows machine". We shared that user-facing environment with the app itself, shelling out for the stuff we couldn't do with libgit2. That has once or twice caused us problems when upgrading since the shell environment could break the ui.
Mac has also shipped with git but their environment has only been used internally by the app and hasn't been made publicly available. A long time ago there was a button in the app to install a command line environment but that was removed after Apple started shipping Git shims in 10.9.
Right now desktop ships with a slimmed down environment for both Mac and Windows which is only meant to be used internally. We need to figure out what we need to do as far as providing a shell environment for users on Windows.
Access to a command line environment is essential for things like conflicts where we currently need to tell the user to go resolve the conflicts themselves. GHfW default cop-out when we hit an unexpected error with git was to let the user launch the shell and figure it out from there (not saying I ever liked that).
Questions
Goals
I know there was talk about a standalone shell thing a while back but I don't know how fleshed out that really was nor do I know if we have time to go for anything other than parity here.
I know this is something near and dear to @shiftkey's heart and I expect him to have a lot to say here, I'm only opening it so that we can start discussing it.