From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Thu, 07 Mar 2024 07:59:27 GMT
Subject: Re: Should --update-refs exclude refs pointing to the current HEAD?
Message-ID: <25aa1b8d-79f6-4b33-be22-735a867367c0@app.fastmail.com>
In-Reply-To: <354f9fed-567f-42c8-9da9-148a5e223022@haller-berlin.de>

On Tue, Mar 5, 2024, at 08:40, Stefan Haller wrote:
> Coming back to this after almost a year, I can say that I'm still
> running into this problem relatively frequently, and it is annoying
> every single time. Excluding refs pointing at the current head from
> being updated, as proposed above, would be a big usability improvement
> for me.

Sounds like a ref-stash command is in order…

    # I want a new branch
    git checkout -b new
    # But I don’t want it to be affected by the next rebase
    git ref-stash push
    git rebase [...]
    # Now I’m done: put the ref back where it was
    git ref-stash pop

-- 
Kristoffer Haugsbakk