Re: [PATCH] branch: let --delete-merged find squash merged branches

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Sep 29, 2026, 08:08 UTC
Message-ID: <d4fd92ea-b1c5-4528-9e9e-0b1ab600891e@app.fastmail.com>
In-Reply-To: <CAHwyqnVf_D3qV1OVYiCnLz2tVteRXdWYTGBaNTJpkVtDwCC1vg@mail.gmail.com>

On Tue, Sep 29, 2026, at 09:52, Harald Nordgren wrote:

Show 22 quoted lines

> On Tue, Sep 29, 2026 at 9:47 AM Kristoffer Haugsbakk
> <kristofferhaugsbakk@fastmail.com> wrote:
>>
>> On Tue, Sep 29, 2026, at 09:30, Harald Nordgren via GitGitGadget wrote:
>> > From: Harald Nordgren <haraldnordgren@gmail.com>
>> >
>> > Branches merged on GitHub with "Squash and merge" or "Rebase and
>> > merge" are never deleted by "git branch --delete-merged". The upstream
>> > holds a rewritten copy of their work, so their tips are not reachable
>> > from it and they look unmerged forever.
>>
>> An example closer to git(1)’s home:
>>
>>     git merge --squash
>>     git commit
>
> True. But likely it opens up the question of _why_ would anyone on
> upstream be doing such destructive actions? Well, then the answer is
> of course that millions of users (including) me do that via GitHub all
> the time.
>
> Maybe I should include both examples in my text.

My *guess* is that `git merge --squash` inspired the forge squashes. But the forges popularized it.

The apparent `git merge --squash` approach of using `git log` for concatenating the commit messages isn’t that nice in my opinion. So I wonder how much it is used.