Skip to content

Instantly share code, notes, and snippets.

@ivanoats
Forked from parndt/gist:958385
Last active November 19, 2022 06:08
Show Gist options
  • Star 9 You must be signed in to star a gist
  • Fork 7 You must be signed in to fork a gist
  • Save ivanoats/1823034 to your computer and use it in GitHub Desktop.
Save ivanoats/1823034 to your computer and use it in GitHub Desktop.
Setting up GIT Bash autocompletion. Use this only if you are using Bash instead of ZSH.

To see what shell you are using, you can:

echo $SHELL and it will tell you.

Use the below only if you are using bash.

Run the following to create ~/.git-completion.bash:

curl https://raw.github.com/git/git/master/contrib/completion/git-completion.bash > ~/.git-completion.bash

and ~/.git-prompt.sh:

curl https://raw.github.com/git/git/master/contrib/completion/git-prompt.sh > ~/.git-prompt.bash

Then add the following to your ~/.bashrc or ~/.bash_profile after PATH:

# Set the base PS1
export PS1="\t: \W$ "

# Source the git bash completion file
if [ -f ~/.git-completion.bash ]; then
    source ~/.git-completion.bash
    source ~/.git-prompt.bash
    PS1='[\u@\h \W$(__git_ps1 " (%s)")]\$ '
fi

export PS1

This will display the branch name next to the folder name in the bash prompt.

@vsee
Copy link

vsee commented Feb 24, 2017

nice piece of code! There is one bug I saw: the second file is called .git-prompt.sh but in bashrc sourced as .git-prompt.bash

@rbrisita
Copy link

To future proof use curl's '-L' option to follow redirects. In its current form the curls won't work on Mac OS X.

@gzalles
Copy link

gzalles commented Jan 23, 2018

can you help me with the path? I have managed to get color scheme and branch showing but not the autocomplete. Thanks!

new to this game...

@KlavierCat
Copy link

The URLs for the curl command need to be updated to https://raw.githubusercontent.com/git/git/master/contrib/completion/git-completion.bash, and https://raw.githubusercontent.com/git/git/master/contrib/completion/git-prompt.sh respectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment