Re: [rebase] `fatal: cannot force update the branch ... checkout out at ...` is confusing when it isn't active
- From
Josh Soref <jsoref@gmail.com>
- Date
- Jul 12, 2023, 20:33 UTC
- Message-ID
- <CACZqfqDE-SCOqVX9a8KCLAn1zSVbYxuCeU8Y=3-nhj5wbL=AWQ@mail.gmail.com>
- In-Reply-To
- <xmqqbkghw4qd.fsf@gitster.g>
Josh Soref writes:
> fatal: cannot force update the branch 'main' checked out at > '/private/var/folders/r3/n29fz25x72x191fdv6mhhr3m0000gp/T/tmp.fGD64HAf'
> It's true git in the repository does have a pin of sorts for the > `main` branch and that `git-rebase` would be very upset if the > branch's location were changed, but as an end user, the `main` branch > is not checked out, the `next` branch is checked out.
Junio C Hamano wrote:
> Fair enough. Perhaps "cannot force update the branch 'main' in use" > would alleviate the confusion?
That would be better.
Even better would be to tell me what's using it (rebase). I'm not sure how possible that is.