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

Git 2.26 rebase.backend change issue

From
BBBastian Buchholz <buchholz.bastian@googlemail.com>
Date
Mar 28, 2020, 08:21 UTC
Message-ID
<CAJTX9qSjnPGKEBDB_ma5QqWOwop5s15kskKQ7EU2ne7VFEBnfA@mail.gmail.com>
Hello,

Just wanted to report that I am running into issues with the git 2.26 `rebase.backend` change. I am a maintainer on https://github.com/FredrikNoren/ungit which is a UI for git using a http server / browser architecture. We are using `git rebase` in non interactive mode (e.g. not specifying `-i` or `--interactive`) on the server and with git 2.26 this fails because it seems that it now runs in interactive mode by default. It tries to an editor on `git rebase --continue`. Specifying `-c rebase.backend=apply` fixes our issue see https://github.com/FredrikNoren/ungit/issues/1301

It would be great if the new merge backend would also support a non interactive mode e.g. by respecting the `-i` or `--interactive` option,

Thanks and regards Bastian Buchholz

Next: Jeff King
Message 1 of 3 in “Git 2.26 rebase.backend change issue”
  1. Bastian BuchholzMar 28, 2020
  2. Jeff KingMar 28, 2020
  3. Bastian BuchholzMar 28, 2020

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.