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

git rebase --continue automatic --skip?

From
Sskillzero@gmail.com <skillzero@gmail.com>
Date
Apr 8, 2011, 20:30 UTC
Message-ID
<BANLkTi=Vc6kB5fvZrqMwDD+yHFb5qENQ8g@mail.gmail.com>

Is there a way to make git rebase --continue automatically do a --skip if a conflict resolution ends up not needing the patch? Normally, git rebase will just silently skip a patch if it's not needed, but if a patch results in a conflict and I use git mergetool and end up deleting all the changes, git rebase --continue stops and makes me explicitly use --skip.

It's a not a big deal, but it happens a lot to me because I do work on a branch that really should have gone on master, but I don't want to disrupt my branch work (i.e. I'm lazy) so I do it directly on the branch then later clean up those commits by isolating the parts that are truly part of the topic vs parts that are unrelated. So I hit a conflict, but want to take the version from master (so the commit disappears from the branch).

Next: Jeff King
Message 1 of 7 in “git rebase --continue automatic --skip?”
  1. skillzero@gmail.comApr 8, 2011
  2. Jeff KingApr 9, 2011
  3. Peter BaumannApr 9, 2011
  4. Junio C HamanoApr 10, 2011
  5. Peter BaumannApr 11, 2011
  6. Junio C HamanoApr 10, 2011
  7. Joshua JuranApr 13, 2011

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.