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

Re: REBASE_HEAD still exists after success end rebase

From
L7Long 76 <long76.git@mail.ru>
Date
Jul 28, 2026, 15:34 UTC
Message-ID
<b19319a0-a248-4213-ab03-b1abb4a42744@mail.ru>
In-Reply-To
<92a69a99-c56f-4ec5-968f-436bef64ee48@gmail.com>
Show 6 quoted lines
> The need for "--force" when pushing is due to you having rebased the 
> branch, it is unrelated to the existence of REBASE_HEAD (other than the 
> fact that it exists indicates you have rebased). Rebasing rewrites the 
> history which means that the remote cannot fast-forward when you push. 
> Rather than using "--force" I'd recommend "--force-with-lease --force- 
> if-includes" instead (see the "git push" man page for more details).

I know it, commit don't the same that was before rebase - because of the conflict, it had to be changed.

Previous: Phillip WoodNext: Long 76
Message 4 of 6 in “REBASE_HEAD still exists after success end rebase”
  1. Long 76Jul 28, 2026
  2. Matt HunterJul 28, 2026
  3. Phillip WoodJul 28, 2026
  4. Long 76Jul 28, 2026
  5. Long 76Jul 28, 2026
  6. Long 76Jul 28, 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.