From: Vincent Mailhol <mailhol@kernel.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Philippe Blain <levraiphilippeblain@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
Ben Knoble <ben.knoble@gmail.com>,
Vincent Mailhol <mailhol@kernel.org>
Subject: [PATCH v3 1/4] completion: add 'git history' subcommands
Date: Thu, 13 Aug 2026 21:05:02 +0200 [thread overview]
Message-ID: <20260813-history_autocompletion-v3-1-69eed1cea93a@kernel.org> (raw)
In-Reply-To: <20260813-history_autocompletion-v3-0-69eed1cea93a@kernel.org>
Use the parse-options completion helpers for the
git history
subcommands and their options. All current history subcommands take a
revision as their first positional argument, so complete that argument
as a revision.
Once the revision is present, leave any further positional arguments to
subcommand-specific completion. This allows a subcommand to complete
another kind of argument, such as the pathspec accepted by
git history split
or another revision if a future subcommand accepts one.
Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
Changes in v3:
- Ignore the split "<option> <value>" syntax for options that take
arguments. This simplifies revision detection and avoids hard-coding
option names.
- Test that options are not completed before a subcommand.
Changes in v2:
- Test options before and after revisions.
- Do not complete options after "--".
- Stop revision completion after the first required revision.
---
contrib/completion/git-completion.bash | 45 ++++++++++++++++++++++++++++++++++
t/t9902-completion.sh | 30 +++++++++++++++++++++++
2 files changed, 75 insertions(+)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index e875787710..1727768487 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -2137,6 +2137,51 @@ _git_help ()
fi
}
+__git_history_has_revision ()
+{
+ local i
+
+ for ((i = __git_cmd_idx + 2; i < cword; i++)); do
+ case "${words[i]}" in
+ -*)
+ ;;
+ *)
+ return 0
+ ;;
+ esac
+ done
+ return 1
+}
+
+_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
+
+ if ! __git_has_doubledash; then
+ case "$cur" in
+ --*)
+ __gitcomp_builtin "history_$subcommand"
+ return
+ ;;
+ esac
+ fi
+
+ if ! __git_history_has_revision; then
+ __git_complete_refs
+ return
+ fi
+}
+
_git_init ()
{
case "$cur" in
diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
index 9ae3c48ebd..d0d8f2ba4a 100755
--- a/t/t9902-completion.sh
+++ b/t/t9902-completion.sh
@@ -3107,6 +3107,36 @@ 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
+ test_completion "git history --" ""
+'
+
+test_expect_success 'git history subcommand options' '
+ test_completion "git history split main --" <<-\EOF &&
+ --update-refs=Z
+ --dry-run Z
+ --no-dry-run Z
+ EOF
+ test_completion "git history fixup --upd" "--update-refs=" &&
+ test_completion "git history fixup --ree" "--reedit-message " &&
+ test_completion "git history split --upd" "--update-refs=" &&
+ test_completion "git history split main --dry" "--dry-run " &&
+ test_completion "git history reword main -- --d" ""
+'
+
+test_expect_success 'git history revisions' '
+ test_completion "git history split ma" "main " &&
+ test_completion "git history split --update-refs=head ma" "main " &&
+ test_completion "git history fixup --empty=drop ma" "main " &&
+ test_completion "git history reword main m" ""
+'
+
test_expect_success 'git reflog show' '
test_when_finished "git checkout - && git branch -d shown" &&
git checkout -b shown &&
--
2.54.0
next prev parent reply other threads:[~2026-08-13 19:05 UTC|newest]
Thread overview: 12+ 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
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
2026-08-13 19:05 ` [PATCH v3 0/4] completion: add support for 'git history' Vincent Mailhol
2026-08-13 19:05 ` Vincent Mailhol [this message]
2026-08-13 19:05 ` [PATCH v3 2/4] completion: complete 'git history --empty' values Vincent Mailhol
2026-08-13 19:05 ` [PATCH v3 3/4] completion: complete 'git history --update-refs' values Vincent Mailhol
2026-08-13 19:05 ` [PATCH v3 4/4] completion: complete 'git history split' pathspecs Vincent Mailhol
2026-08-13 20:30 ` [PATCH v3 0/4] completion: add support for 'git history' Kristoffer Haugsbakk
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=20260813-history_autocompletion-v3-1-69eed1cea93a@kernel.org \
--to=mailhol@kernel.org \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@gmail.com \
--cc=ps@pks.im \
/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