The official FAQ of bash-completion contains very interesting information.
First, if you are 100% sure your $BASH_COMPLETION_USER_DIR and $XDG_DATA_HOME environment variable are empty, what you specified in your original question is a good place to add your own bash-completion scripts:
~/.local/share/bash-completion/completions/git
To be noted .bash extension not necessary.
The fact is that bash-completion scripts are loaded thanks to the /etc/profile.d/bash_completion.sh file.
If you perform something in your .bashrc file, you would somehow break something in the loading chain.
Nevertheless, if you override existing completion function, you still need to ensure the loading order is correct. So loading first bash-completion script is mandatory to ensure everything ends successfully. You can easily perform it, adding this initial instruction at the beginning of your ~/.local/share/bash-completion/completions/git file:
# Ensures git bash-completion is loaded before overriding any function (be careful to avoid endless loop). ! complete -p git &> /dev/null && [ ${ENDLESS_LOOP_SAFEGUARD:-0} -eq 0 ] && ENDLESS_LOOP_SAFEGUARD=1 BASH_COMPLETION_USER_DIR=/dev/null _completion_loader git
First it checks if git bash-completion has already been loaded, and then if this is not the case, all the bash-completion git definition are loaded. Edit: the ENDLESS_LOOP_SAFEGUARD trick allows to avoid endless loop when this is the first time bash completion is loading git part.
If needed, you can get the usage:
complete --help
complete: complete [-abcdefgjksuv] [-pr] [-DE] [-o option] [-A action] [-G globpat] [-W wordlist] [-F function] [-C command] [-X filterpat] [-P prefix] [-S suffix] [name ...] Specify how arguments are to be completed by Readline.
For each NAME, specify how arguments are to be completed. If no options are supplied, existing completion specifications are printed in a way that allows them to be reused as input.
Options:
-p print existing completion specifications in a reusable format -r remove a completion specification for each NAME, or, if no NAMEs are supplied, all completion specifications -D apply the completions and actions as the default for commands without any specific completion defined -E apply the completions and actions to "empty" commands -- completion attempted on a blank line
When completion is attempted, the actions are applied in the order the uppercase-letter options are listed above. The -D option takes precedence over -E.
Exit Status: Returns success unless an invalid option is supplied or an error occurs.
Then, and only then, you can define whatever you want, including your old way to override git clone bash completion:
# Ensures git bash-completion is loaded before overriding any function (be careful to avoid endless loop). ! complete -p git &> /dev/null && [ ${ENDLESS_LOOP_SAFEGUARD:-0} -eq 0 ] && ENDLESS_LOOP_SAFEGUARD=1 BASH_COMPLETION_USER_DIR=/dev/null _completion_loader git # https://github.com/scop/bash-completion/blob/d2f14a7/bash_completion#L498 __ltrim_colon_completions() { if [[ "$1" == *:* && "$COMP_WORDBREAKS" == *:* ]]; then # Remove colon-word prefix from COMPREPLY items local colon_word=${1%"${1##*:}"} local i=${#COMPREPLY[*]} while [[ $((--i)) -ge 0 ]]; do COMPREPLY[$i]=${COMPREPLY[$i]#"$colon_word"} done fi } _git_clone() { case "$cur" in --*) __gitcomp_builtin clone return ;; *) argc=0 for word in "${words[@]}"; do case "$word" in git|clone|--*) continue ;; *) argc=$((argc + 1)) ;; esac done if [ $argc -le 1 ]; then __gitcomp "https://github.com/git/git https://github.com/python/cpython" __ltrim_colon_completions "$cur" fi ;; esac }
Each time you perform change and want to check result, you just need to request bash-completion reload for git:
_completion_loader git
Such a way, you will never lost your change, because you let the package files untouched; and still can enhanced any existing bash-completion with your own functions.
Edit:
About your fear with _completion_loader function => , but after having checked the source code, this function exists since commit cad3abfc7, of 2015-07-15 20:53:05 so I guess it should be kept backward-compatible, but true without guarantee. I'll edit my anwer to propose some alternatives
As alternative, this should be another way to get your own git completion definition (to put at beginning of your own script):
# Ensures git bash-completion is loaded before overriding any function # Be careful to avoid endless loop with dedicated $ENDLESS_LOOP_SAFEGUARD environment variable. if ! complete -p git &> /dev/null && [ ${ENDLESS_LOOP_SAFEGUARD:-0} -eq 0 ]; then # Trick: define $BASH_COMPLETION_USER_DIR environment variable here to ensure bash-completion rule are loaded once. export BASH_COMPLETION_USER_DIR=/usr/share complete -D git unset BASH_COMPLETION_USER_DIR ENDLESS_LOOP_SAFEGUARD=1 complete -D git fi
__load_completionyourself, and then override like you used to?