Re: REBASE_HEAD still exists after success end rebase

On Tue Jul 28, 2026 at 4:26 AM EDT, Long 76 wrote:
>
> 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!

I ran into this not that long ago too, while working on a script.  It
looked like this behavior depended on how the _last_ item in the rebase
todo list was handled.  I found if the last action was a squash or edit
(I don't think reword did this), then REBASE_HEAD was left behind.

Also, if rebase stops on a break command, then REBASE_HEAD will be
missing, even though a rebase is still in-progress.

I made a very short-lived effort to look into why this "bug" was
happening.  I say "bug" in quotes, because I'm not even sure if it is
even problematic behavior.

I solved my need at the time (detecting a rebase in progress) by
checking for the existence of either of the 'rebase-merge' or
'rebase-apply' directories in $GIT_DIR.
>
> --
> Long76