# git interactive rebase does not allow editing commits at once anymore

3 messages from 2026-04-30 to 2026-04-30. Participants: David Jordanes, Junio C Hamano, Phillip Wood.
Thread: https://gitlist.dev/t/65568

## David Jordanes, 2026-04-30 07:46

Subject: git interactive rebase does not allow editing commits at once anymore
Message-ID: <DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com>

```
Git version: git version 2.53.0.windows.2
OS: Windows 11

Steps to reproduce:
1. Create a dummy repo
2. Create a couple of commits
2. Run git rebase -i HEAD~2

Observed:
Lines in todo appear as:
pick <hash> # commit 1
pick <hash> # commit 2

After editing:
reword <hash> commit A
reword <hash> commit B

Then git loops each commit to edit. 

Expected:
After editing, all changes should be applied at once (no loop).

Question:
Is this intended behavior? By whom and why this flow was decided? What problem it solves? If I have to rebase interactively 10 or 15 commits I have to go through all those commits one by one???
```

## Junio C Hamano, 2026-04-30 09:29

Subject: Re: git interactive rebase does not allow editing commits at once anymore
Message-ID: <xmqqo6j0zthw.fsf@gitster.g>
In-Reply-To: <DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com>

```
David Jordanes <davidjordanes@outlook.com> writes:

> Git version: git version 2.53.0.windows.2
> OS: Windows 11

I do not do Windows, but I am curious about "anymore" part of your
message title.  Are you reporting a regression?

```

## Phillip Wood, 2026-04-30 13:43

Subject: Re: git interactive rebase does not allow editing commits at once anymore
Message-ID: <986ca9b2-2ad1-4b2e-a61f-3407fe5d5251@gmail.com>
In-Reply-To: <DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com>

```
Hi David

On 30/04/2026 08:46, David Jordanes wrote:
> Git version: git version 2.53.0.windows.2
> OS: Windows 11
> 
> Steps to reproduce:
> 1. Create a dummy repo
> 2. Create a couple of commits
> 2. Run git rebase -i HEAD~2
> 
> Observed:
> Lines in todo appear as:
> pick <hash> # commit 1
> pick <hash> # commit 2
> 
> After editing:
> reword <hash> commit A
> reword <hash> commit B
> 
> Then git loops each commit to edit.

If you mean git opens the editor for you to edit the first commit 
message and then when you close the editor it opens the second message, 
it is working as it always has done. There is an external program called 
"git-revise" which I believe lets you edit multiple commit message at 
once though I've not used it myself.

Processing the commits one at a time lets you inspect the changes for 
the commit you're editing the message for and if you have 
"commit.verbose" enabled then git will show you the diff for the commit 
below the commit message in the editor.

Thanks

Phillip


> Expected:
> After editing, all changes should be applied at once (no loop).
> 
> Question:
> Is this intended behavior? By whom and why this flow was decided? What problem it solves? If I have to rebase interactively 10 or 15 commits I have to go through all those commits one by one???


```