git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git interactive rebase does not allow editing commits at once anymore

From
DJDavid Jordanes <davidjordanes@outlook.com>
Date
Apr 30, 2026, 07:46 UTC
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???

Next: Junio C Hamano
Message 1 of 3 in “git interactive rebase does not allow editing commits at once anymore”
  1. David JordanesApr 30, 2026
  2. Junio C HamanoApr 30, 2026
  3. Phillip WoodApr 30, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.