The Workspaces function in VSCode allows you to have an independent 'profile' for your project allowing it to have it's own set of specific settings, and Extensions that are enable/disabled for it, etc. To create a Workspace in VSCode: Open your Project's folder by going to File and selecting Open Folder.... Save it by going to File and selecting Save Workspace As.... You can now use the newly created .code-workspace file as a shortcut to your Project's workspace instead of launching VSCode directly. Keep in mind that the .code-workspace file stores the workspace specific settings so keep it somewhere safe. I keep mine in the root folder that stores all of my project repositories. You can always make a shortcut of it on your desktop for more convenient access.I personally like to disable most Extensions globally in VSCode and only enable the ones that are relevant to each Workspace. This helps to reduce the load VSCode puts on your system if you use a lot of different Extensions across your projects.

Set VS Code as default diff tool git config --global diff.tool vscode git config --global difftool.vscode.cmd 'code --wait --diff $LOCAL $REMOTE'

shell: #!/usr/bin/env bash ## # Interactive search. # [[ -n $1 ]] && cd "$1" # go to provided folder or noop export FZF_DEFAULT_COMMAND="rg --column --line-number --no-heading --color=always -- ''" selected=$( fzf \ --ansi \ --delimiter : \ --bind "f12:execute-silent:(code -g $PWD/{1..3})" \ --preview-window 'up,60%,border-bottom,+{2}+3/3,~3' \ --preview 'bat -f --highlight-line={2} {1}' | cut -d":" -f1,2,3 ) [[ -n $selected ]] && code -g "$PWD"/"$selected" For example, on macOS, you can copy the script, then run this in your terminal: pbpaste > ~/bin/rgf # ~/bin is in my $PATH chmod +x ~/bin/rgf