Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH v3 0/3] completion of 'git [-C <dir>] checkout'
Date: Thu, 13 Aug 2026 12:12:31 -0700	[thread overview]
Message-ID: <20260813191234.1066662-1-gitster@pobox.com> (raw)
In-Reply-To: <xmqq7blx5oor.fsf@gitster.g>

Continuing from the previous 'git [-C <dir>] diff' series, these
patches correct completion for 'git checkout [-C <dir>] path<TAB>',
with a fallback to complete untracked paths of somewhat dubious
value, primarily as a reminder for future work.

Hopefully this will be the small and final update to the series.

 1/3: completion: no-op refactoring of checkout completion
 2/3: completion: complete tracked paths for "git checkout"
 3/3: completion: 'git checkout' completes untracked paths as a last
        resort

 contrib/completion/git-completion.bash | 88 ++++++++++++++------------
 t/t9902-completion.sh                  | 56 ++++++++++++++++
 2 files changed, 105 insertions(+), 39 deletions(-)

Range-diff against v2:
1:  33d136ffde = 1:  33d136ffde completion: no-op refactoring of checkout completion
2:  a28754cfd9 = 2:  a28754cfd9 completion: complete tracked paths for "git checkout"
3:  90aec6539c ! 3:  17880068c0 completion: 'git checkout' completes untracked paths as a last resort
    @@ contrib/completion/git-completion.bash: _git_checkout ()
      	fi
     +
     +	if [ ${#COMPREPLY[@]} -eq 0 ]; then
    -+		__git_complete_index_file "--others"
    ++		__git_complete_index_file "--others --directory"
     +	fi
      }
      
-- 
2.55.0-759-g9dcc51a0fd


  parent reply	other threads:[~2026-08-13 19:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  3:19 [PATCH 0/2] completion of 'git [-C <dir>] checkout' Junio C Hamano
2026-08-11  3:21 ` [PATCH 1/2] completion: no-op refactoring of checkout completion Junio C Hamano
2026-08-11  3:21 ` [PATCH 2/2] completion: complete tracked paths for "git checkout" Junio C Hamano
2026-08-11 16:32   ` Ben Knoble
2026-08-11 17:25     ` Junio C Hamano
2026-08-11  4:04 ` [PATCH 0/2] completion of 'git [-C <dir>] checkout' Junio C Hamano
2026-08-11 16:33   ` Ben Knoble
2026-08-12  1:45     ` Junio C Hamano
2026-08-12 16:48 ` [PATCH v2 0/3] " Junio C Hamano
2026-08-12 16:48   ` [PATCH v2 1/3] completion: no-op refactoring of checkout completion Junio C Hamano
2026-08-12 16:48   ` [PATCH v2 2/3] completion: complete tracked paths for "git checkout" Junio C Hamano
2026-08-12 16:48   ` [PATCH v2 3/3] completion: 'git checkout' completes untracked paths as a last resort Junio C Hamano
2026-08-12 19:57     ` Elijah Newren
2026-08-12 20:18       ` Junio C Hamano
2026-08-13 19:12 ` Junio C Hamano [this message]
2026-08-13 19:12   ` [PATCH v3 1/3] completion: no-op refactoring of checkout completion Junio C Hamano
2026-08-13 19:12   ` [PATCH v3 2/3] completion: complete tracked paths for "git checkout" Junio C Hamano
2026-08-13 19:12   ` [PATCH v3 3/3] completion: 'git checkout' completes untracked paths as a last resort Junio C Hamano
2026-08-14  1:53   ` [PATCH v3 0/3] completion of 'git [-C <dir>] checkout' Elijah Newren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260813191234.1066662-1-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox