GitPortable is not portable about gitportable

[sheabunge]

It sounds like you downloaded the regular version of Git for Windows, not the PortableApps.com-packaged version from this repository.

You can download the portable installer from https://github.com/sheabunge/GitPortable/releases/latest

Once downloaded, open Git by clicking on the GitBashPortable.exe launcher. Running a command like

git config --global --list --show-origin

will confirm that configuration is being loaded from the GitPortable/Data/home/.gitconfig file instead of from the local machine.

[CaliforniaMountainSnake]

Thanks, https://github.com/sheabunge/GitPortable/releases/latest version seems really portable.

But I don't understand why this version is not portable:

[sheabunge]

That is a different product, released by the Git for Windows project. It's really just a version of Git that you can extract to a directory instead of needing to install. It may be a little misleadingly named, but have nothing to do with its development or release whatsoever, so you'll need to take it up with them.

Nevertheless, the lack of true portability in that version is primarily what makes this one useful – it adds the portable configuration possibilities that aren't present in the original project.

[LeonT-A]

Nevertheless, the lack of true portability in that version is primarily what makes this one useful – it adds the portable configuration possibilities that aren't present in the original project.

May I ask what these are? @sheabunge

I just spent a week figuring out how to get the above mentioned portable version of Git for Windows to actually be portable (Didn't notice this repo). My biggest concern is being able to update to the newest release of Git for windows, which if I read right your release does support manual upgrades?

What I ended up doing to the Git for Windows release is writing and compiling a python script to set a custom HOME variable that is relative to git-bash.exe. The script then launches git-bash.exe, which inherits that HOME variable and uses it. In essence a wrapper for the wrapper (git-bash.exe). Before doing this things would get written to my C:\Users\USERNAME folder, but after this I don't see anything being left behind by either Git-Bash or its built-in programs. To upgrade I just have to replace the files with a simple copy paste of the newest portable release. Since I compiled it into a .exe, it shows up in the PortableApps Launcher and works just fine (I just hide the original git-bash.exe).

Just curious if there's something more I'm missing with my setup that you include in yours. I also use PortableApps, though some of my programs (Like Git-Bash) are just portable versions released directly by the publisher (mirc for example)

[sheabunge]

@LeonT-A This package of Git for Windows uses the PortableApps.com launcher configuration to set the HOME variable to a portable data folder, as well as rewriting absolute paths in .gitconfig to prevent things from breaking if the directory or drive letter changes.