From: Patrick Steinhardt <ps@pks.im>
To: Vincent Mailhol <mailhol@kernel.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] completion: add 'git history' subcommands
Date: Wed, 5 Aug 2026 08:19:43 +0200 [thread overview]
Message-ID: <anLV__4THdvugj8f@pks.im> (raw)
In-Reply-To: <20260804-history_autocompletion-v1-1-6f7459ffb677@kernel.org>
On Tue, Aug 04, 2026 at 09:56:32PM +0200, Vincent Mailhol wrote:
> Use the parse-options completion helpers for the "git history"
> subcommands and their options. Complete positional arguments as
> revisions, and add coverage for each kind of completion.
Ah, great! I wanted to write shell completion for git-history(1) for a
while but never really found the time to actually do it.
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index e875787710..f10813c8d7 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -2137,6 +2137,30 @@ _git_help ()
> fi
> }
>
> +_git_history ()
> +{
> + local subcommands subcommand
> +
> + __git_resolve_builtins "history"
> +
> + subcommands="$___git_resolved_builtins"
> + subcommand="$(__git_find_subcommand "$subcommands")"
> +
> + if [ -z "$subcommand" ]; then
> + __gitcomp "$subcommands"
> + return
> + fi
Okay. We first try to figure out whether there is any subcommand passed
by the user already. If not, we complete available subcommands.
> + case "$cur" in
> + --*)
> + __gitcomp_builtin "history_$subcommand"
> + ;;
> + *)
> + __git_complete_refs
> + ;;
> + esac
> +}
Otherwise we try to either complete available options if we see a
leading "--", or alternatively we complete references. This works well
for "drop", "fixup" and "reword".
The one command where this falls flat a bit is `git history split`.
While the first non-option argument is indeed a reference, subsequent
arguments are pathspecs. So ideally, we'd notice that we already have a
reference there and, if so, complete file paths.
But that being said, I think this is a good-enough first iteration and a
strict improvement over the status quo -- we don't have to be perfect
right from the start. So if you want to also make that case work then
great, but I won't insist on it.
> diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
> index 9ae3c48ebd..08ecf682ed 100755
> --- a/t/t9902-completion.sh
> +++ b/t/t9902-completion.sh
> @@ -3107,6 +3107,23 @@ test_expect_success 'git clone --config= - value' '
> EOF
> '
>
> +test_expect_success 'git history subcommands' '
> + test_completion "git history " <<-\EOF
> + drop Z
> + fixup Z
> + reword Z
> + split Z
> + EOF
> +'
This will cause conflicts with "seen", as there's a new upcoming
"squash" command that's currently cooking there. That's fine though,
nothing you can do about that.
Thanks!
Patrick
next prev parent reply other threads:[~2026-08-05 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 19:56 [PATCH] completion: add 'git history' subcommands Vincent Mailhol
2026-08-05 6:19 ` Patrick Steinhardt [this message]
2026-08-05 11:56 ` D. Ben Knoble
2026-08-05 16:15 ` Junio C Hamano
2026-08-05 21:20 ` Vincent Mailhol
2026-08-06 5:18 ` Patrick Steinhardt
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=anLV__4THdvugj8f@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@gmail.com \
--cc=mailhol@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.