From: Long 76 <long76.git@mail.ru>
To: git@vger.kernel.org
Subject: REBASE_HEAD still exists after success end rebase
Date: Tue, 28 Jul 2026 11:26:29 +0300 [thread overview]
Message-ID: <edfc868b-6be6-4871-a539-e70791db216d@mail.ru> (raw)
Hi,
My configuration:
OS Kubuntu 24.04
Git version: 2.54.0 from ppa:git-core/ppa
.gitconfig
[merge]
guitool = meld
tool = meld
[core]
editor = code -w
autocrlf = input
quotePath = false
eol = lf
[global]
[diff]
tool = meld
[gui]
editor = code
[fetch]
prune = true
[mergetool]
keepBackup = false
How to reproduce:
1) Made repo
# Init repo with README.md
git init
echo -e '# Git rebase bug\n\n```\ngit rebase master\ngit mergetool\ngit
rebase --continue\ngit rev-parse REBASE_HEAD\n```' > README.md
git add README.md
git commit -m "docs: add README.md"
# Add feature branch
git branch feature_branch
# Add files in separate commits
echo -e "Text 1 line\nText 2 line\nText 3 line\nText 4 line\nText 5
line" > Text1.txt
git add Text1.txt
git commit -m "feat: add Text1.txt"
echo -e "Text 1 line\nText 2 line\nText 3 line\nText 4 line\nText 5
line" > Text2.txt
git add Text2.txt
git commit -m "feat: add Text2.txt"
echo -e "Text 1 line\nText 2 line\nText 3 line\nText 4 line\nText 5
line" > Text3.txt
git add Text3.txt
git commit -m "feat: add Text3.txt"
# Do the same in feature branch and one more in one commit
git checkout feature_branch
echo -e "Texts 1 line\nTexts 2 line\nTexts 3 line\nText 4 line\nTexts 5
line" > Text1.txt
git add Text1.txt
echo -e "Text 1 line\nText 2 line\nText 3 line\nText 4 line\nText 5
line" > Text2.txt
git add Text2.txt
echo -e "Texts 1 line\nTexts 2 line\nTexts 3 line\nText 4 line\nTexts 5
line" > Text3.txt
git add Text3.txt
echo -e "Texts 1 line\nTexts 2 line\nText 3 line\nTexts 4 line\nText 5
line" > Text4.txt
git add Text4.txt
git commit -m "feat: add all files"
2) Call — git rebase master
3) Call — git mergetool
4) Call — git rebase --continue
5) Call — git rev-parse REBASE_HEAD
Last command return value and .git/REBASE_HEAD exists.
In other words REBASE_HEAD exists if ogirinal commit in new branch
modified and need call git push --force to send it to server. Please fix
it, thanks!
--
Long76
next reply other threads:[~2026-07-28 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 8:26 Long 76 [this message]
2026-07-28 9:39 ` REBASE_HEAD still exists after success end rebase Matt Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=edfc868b-6be6-4871-a539-e70791db216d@mail.ru \
--to=long76.git@mail.ru \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox