![]() ![]() There's a few places we expose Git Shell in the current Desktop (the "Open in Git Shell" context menu being the most prominent) and we could conditionally enable these when they have this other component installed. For others, they might want to "graduate" to the command line, so being able to install Git Shell at some point in the future would be appealing. For some beginners, they might have no interest in touching the command line. I'd love to keep this number as lean as possible, and having optional components would be one way to achieve that. We have an installer size currently of ~70MB on macOS and 85MB on Windows. Extract Git Shell component into it's own project We also have machine-wide installs supported out of the box with TNG, so a machine-wide Git Shell experience is now achievable. Having all of this in one location is really neat. This is the sort of friction we've loved to □ over the years, irrespective of the user's experience with Git. We've a bunch of experience with tweaking Git to take away friction (think Enterprise environment with certificates in the Certificate Store, and having those mirrored so libcurl works fine). This has significant interest from our Windows audience, especially going back to The Bad Old Days. It's more work for us to manage and maintain, but gives us full control over the experience. This could look a lot like what we have now, with "Open in Git Shell" shortcuts to make it easy for people to jump out of the GUI and into a shell. Continue to have an in-the-box experience I'm very much □ on ensuring we interoperate with the embedded Git that we ship in TNG - raised some excellent points in #184 (comment) about the implementation, which we need to think about, but I wanted to approach this from the big picture. With the change to using an embedded Git for both platforms, this means we no longer need to have this available to users at the very beginning, which makes this an opportunity to do something different. "the easiest way to get git running on your windows machine" I know this is something near and dear to heart and I expect him to have a lot to say here, I'm only opening it so that we can start discussing it. 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. Provide an opinionated environment with sane defaults and credential support.Provide a super simple way to get Git onto your Windows machine.Do we want to allow custom shells in options like we do today.What kind of interoperability do we want between our internal env and git shell (see How should we handle git authentication? #184).How do we ship it? Exactly as we do today? 7-zip archive unpacked to magic dir and environment launched through GitHub.exe?.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). ![]() We need to figure out what we need to do as far as providing a shell environment for users on Windows.Īccess 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. Right now desktop ships with a slimmed down environment for both Mac and Windows which is only meant to be used internally. 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. Mac has also shipped with git but their environment has only been used internally by the app and hasn't been made publicly available. That has once or twice caused us problems when upgrading since the shell environment could break the ui. We shared that user-facing environment with the app itself, shelling out for the stuff we couldn't do with libgit2. It's always been a big selling point, "the easiest way to get git running on your windows machine". GitHub for Windows has always shipped with a complete git/bash command line environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |