From: Phillip Wood <phillip.wood123@gmail.com>
To: mail@abhinavg.net, git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] rebase: ignore non-branch update-refs
Date: Thu, 7 May 2026 17:08:24 +0100 [thread overview]
Message-ID: <dc7c32f7-d56e-4dd6-977e-cced6155e758@gmail.com> (raw)
In-Reply-To: <20260506023944.90691-1-mail@abhinavg.net>
Hi Abhinav
On 06/05/2026 03:39, mail@abhinavg.net wrote:
> From: Abhinav Gupta <mail@abhinavg.net>
>
> The following Git configuration breaks git rebase --update-refs:
>
> [rebase]
> instructionFormat = %s%d
>
> The '%d' format requests all available decorations for a commit,
> filling the global decoration table with all of them,
> which --update-refs then uses to populate 'update-ref' instructions
> in the rebase todo list.
>
> Specifically, this results in the following instruction:
>
> update-ref HEAD
>
> The todo parser then rejects the instruction:
>
> error: update-ref requires a fully qualified refname e.g. refs/heads/HEAD
> error: invalid line 3: update-ref HEAD
>
> To fix, ignore decorations that are not local branches
> when scanning through the table.
Thanks for the clear explanation, the solution makes sense
> diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
> index 3e44562afa..d58236f0eb 100755
> --- a/t/t3404-rebase-interactive.sh
> +++ b/t/t3404-rebase-interactive.sh
> @@ -1960,6 +1960,28 @@ test_expect_success '--update-refs adds commands with --rebase-merges' '
> )
> '
>
> +test_expect_success '--update-refs ignores non-branch decorations' '
> + test_when_finished "git branch -D update-refs" &&
> + test_when_finished "git branch -D third" &&
I'm not sure that we really need to create this branch in the first
place. We already create update-refs from no-conflict-branch so we can
check that no-conflict-branch appears and update-refs does not. In
addition to checking that HEAD does not appear we should also check that
we don't try to update any tags (HEAD matches tag M). I think the
simplest way is to check the output of "grep ^update-ref todo" so we'd
have
test_expect_success '--update-refs ignores non-branch decorations' '
test_when_finished "git branch -D update-refs" &&
test_when_finished "git checkout primary" &&
git checkout -B update-refs no-conflict-branch &&
(
set_cat_todo_editor &&
# rebase.instructionFormat=%d loads normal log decorations before
# --update-refs adds its branch placeholders so we must ignore
# all non-local decorations.
test_must_fail git -c rebase.instructionFormat="%s%d" \
rebase -i --update-refs HEAD^ >todo
) &&
grep ^update-ref todo >actual &&
test_write_lines "update-ref refs/heads/no-conflict-branch" >expect &&
test_cmp expect actual
'
Thanks for working on this
Phillip
> + test_when_finished "git checkout primary" &&
> + git checkout -B update-refs no-conflict-branch &&
> + git branch -f third HEAD~1 &&
> + (
> + set_cat_todo_editor &&
> +
> + # rebase.instructionFormat=%d loads normal log decorations before
> + # --update-refs adds its branch placeholders.
> + # The placeholder scan must still ignore symbolic decorations,
> + # because "update-ref HEAD" is not a valid branch update.
> + test_must_fail git -c rebase.instructionFormat="%s%d" \
> + rebase -i --update-refs primary >todo &&
> +
> + test_grep "^update-ref refs/heads/third$" todo &&
> + test_grep ! "^update-ref refs/heads/update-refs$" todo &&
> + test_grep ! "^update-ref HEAD$" todo
> + )
> +'
> +
> test_expect_success '--update-refs updates refs correctly' '
> git checkout -B update-refs no-conflict-branch &&
> git branch -f base HEAD~4 &&
>
> base-commit: 94f057755b7941b321fd11fec1b2e3ca5313a4e0
next prev parent reply other threads:[~2026-05-07 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 2:39 [PATCH] rebase: ignore non-branch update-refs mail
2026-05-07 16:08 ` Phillip Wood [this message]
2026-05-08 1:58 ` [PATCH v2] " mail
2026-05-08 10:07 ` Phillip Wood
2026-05-10 22:41 ` [PATCH v3 0/1] " mail
2026-05-10 22:41 ` [PATCH v3 1/1] " mail
2026-05-10 1:11 ` [PATCH] " Junio C Hamano
2026-05-10 13:37 ` Phillip Wood
2026-05-10 23:37 ` Junio C Hamano
2026-05-11 0:15 ` Abhinav Gupta
2026-05-11 0:20 ` Junio C Hamano
2026-05-11 0:33 ` Abhinav Gupta
2026-05-12 15:10 ` Phillip Wood
2026-05-15 15:40 ` Phillip Wood
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=dc7c32f7-d56e-4dd6-977e-cced6155e758@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mail@abhinavg.net \
--cc=phillip.wood@dunelm.org.uk \
--cc=stolee@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