Disable auto-completion of remote branches in Git Bash?

by

With Git 2.13 (Q2 2017), you can disable (some of) the branch completion.

git checkout --no-guess ...
# or:
export GIT_COMPLETION_CHECKOUT_NO_GUESS=1

See commit 60e71bb (21 Apr 2017) by Jeff King (peff).
(Merged by Junio C Hamano — gitster — in commit b439747, 01 May 2017)

As documented in contrib/completion/git-completion.bash now:

You can set the following environment variables to influence the behavior of the completion routines:

GIT_COMPLETION_CHECKOUT_NO_GUESS

When set to “1”, do not include “DWIM” suggestions in git-checkout
completion (e.g., completing “foo” when “origin/foo” exists).

Note: DWIM is short for Do What I Mean, where a system attempts to anticipate what users intend to do, correcting trivial errors automatically rather than blindly executing users’ explicit but potentially incorrect inputs.

completion: optionally disable checkout DWIM

When we complete branch names for “git checkout“, we also complete remote branch names that could trigger the DWIM behavior. Depending on your workflow and project, this can be either convenient or annoying.

For instance, my clone of gitster.git contains 74 local “jk/*” branches, but origin contains another 147.
When I want to checkout a local branch but can’t quite remember the name, tab completion shows me 251 entries. And worse, for a topic that has been picked up for pu, the upstream branch name is likely to be similar to mine, leading to a high probability that I pick the wrong one and accidentally create a new branch.

Note: “picked up for pu”: see a What’s cooking in git.git: it starts with:

Commits prefixed with ‘-‘ are only in ‘pu‘ (proposed updates) while commits prefixed with ‘+‘ are in ‘next‘.

This is part of the Git Workflow Graduation process.

pu (proposed updates) is an integration branch for things that are not quite ready for inclusion yet

This patch adds a way for the user to tell the completion
code not to include DWIM suggestions for checkout.
This can already be done by typing:

git checkout --no-guess jk/<TAB>

but that’s rather cumbersome.

The downside, of course, is that you no longer get completion support when you do want to invoke the DWIM behavior.
But depending on your workflow, that may not be a big loss (for instance, in git.git I am much more likely to want to detach, so I’d type “git checkout origin/jk/<TAB>” anyway).

More Related Contents:

  1. Remove credentials from Git
  2. Git symbolic links in Windows
  3. Filename too long in Git for Windows
  4. Git – How to use .netrc file on Windows to save user and password
  5. How can I set up an editor to work with Git on Windows?
  6. ‘git’ is not recognized as an internal or external command
  7. Git on Windows, “Out of memory – malloc failed”
  8. Unable to resolve “unable to get local issuer certificate” using git on Windows with self-signed certificate
  9. Git on Windows: How do you set up a mergetool?
  10. Git for Windows: .bashrc or equivalent configuration files for Git Bash shell
  11. Git with SSH on Windows
  12. ‘chcp’ is not recognized as an internal or external command, operable program or batch file. on a Windows PC
  13. How to make git ignore changes in case?
  14. Threadscope’s gettext.sh file interferes with git on Windows
  15. Changing .gitconfig location on Windows
  16. What happens when I clone a repository with symlinks on Windows?
  17. Permission denied (publickey) when setting up Jenkins
  18. How to prevent that the password to decrypt the private key has to be entered every time when using Git Bash on Windows?
  19. Concurrency in a GIT repo on a network shared folder
  20. ‘ssh-keygen’ is not recognized as an internal or external command
  21. Error “‘git’ is not recognized as an internal or external command”
  22. how do I clone files with colons in the filename
  23. Git file permissions on Windows
  24. Git rename from index.lock to index failed
  25. Why is “MINGW64” appearing on my Git bash?
  26. Git fatal: remote end hung up
  27. sh.exe.stackdump when use git stash
  28. How to update git version from GitHub Desktop on Windows
  29. docker error on windows : the input device is not a TTY. If you are using mintty, try prefixing the command with ‘winpty’ [duplicate]
  30. Out of a git console: how do I execute a batch file and then return to git console?

Leave a Comment