git/list[1] front-page[2] threads[3] people[4] search[5] about
 

bash completion bug: "symbolic-ref" subcommand doesn't complete

From
AAndrey <butirsky@gmail.com>
Date
Mar 12, 2026, 16:14 UTC
Message-ID
<c1e0c05b-c767-4fcc-859a-4da6b90c4497@gmail.com>

Bash can't complete some commands, e.g. symbolic-ref, bugreport, maybe others.

These commands are not seen in the completion output:
|$ git #press Tab
add               blame             citool            diff         gitk  
             log               prune  refs              restore          
  show submodule
am                branch            clean             difftool         
grep              maintenance       pull remote            revert        
     show-branch       switch
apply             bundle            clone             fetch        gui  
              merge             push repack            rm                
sparse-checkout   tag
archive           checkout          commit format-patch      help        
       mergetool  range-diff        replace           scalar            
stage          whatchanged
backfill          cherry            config            fsck         init  
             mv                rebase request-pull      send-email      
   stash             worktree
bisect            cherry-pick       describe          gc         
instaweb          notes             reflog reset             shortlog    
       status |
|
|
There is no such problem with Zsh.

[System Info] GNU bash, version 5.3.0(1)-release (x86_64-redhat-linux-gnu) git version 2.53.0 rust: disabled gettext: enabled libc info: glibc: 2.42

Next: Junio C Hamano
Message 1 of 4 in “bash completion bug: "symbolic-ref" subcommand doesn't complete”
  1. AndreyMar 12, 2026
  2. Junio C HamanoMar 12, 2026
  3. AndreyMar 12, 2026
  4. AndreyMar 12, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.