Set up SSH with Sourcetree on Windows
E.g rename the branch mybranch to feature/mybranch will make it appear under the folder feature in Sourcetree.
I got this message ‘fatal: unable to access ‘\/.config/git/config’: Invalid argument’ when opening a GIT based solution in VS 2017.
Solution was to add an environment variable “HOME” with value “c:\” (c: or where your project folder resides).
Solution info here:
If you have a config file or something similar you change on your local computer but dont want it to get marked as “modified”.
Use this command:
git update-index --skip-worktree [filename]
If remote repo gets an update on that file you will get notified about this on a pull.
skip-worktree is useful when you instruct git not to touch a specific file ever. That is useful for an already tracked config file.
Upstream main repository hosts some production-ready config but you would like to change some settings in the config to be able to do some local testing. And you don’t want to accidentally check the changes in such file to affect the production config. In that case
skip-worktree makes perfect scene.
If you have skip-worktree on a file and the upstream changes, you get “please commit or stash” when you try to pull
My SourceTree GIT manager was freezing for 5-10 seconds when switching between repositories.
These commands fixed the issue:
$ git config --global core.preloadindex true
$ git config --global core.fscache true
$ git config --global gc.auto 256
Also in combination with adding GIT program folder and SourceTree program folder to excluded paths for Windows Defender (antivirus scanner). The switch between tabs is now instant.
You simply need to remove three files from the project Path. navigate to Your Project Folder then permanently delete (“SHIFT + DEL”)
the files to permanently delete are: (‘File’ .gitignore ,’File’ .gitattributes , and ‘folder’.git)
(may be hidden so ensure you have your folders and search options > View > show hidden files, folder, and drives(Radio Button) Selected)…reopen VS and their is no more relationship to the Git Source Control. if you wanted to take it as far as removing it from the registry as mentioned above you could but shouldn’t be necessary aside from the “house keeping” of your machine. hope this helps.