From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Tue, 03 Dec 2024 17:42:43 GMT
Subject: Re: Detecting squash-merged branches (and question about git-diff-tree)
Message-ID: <95b88ece-8188-46aa-b263-61bb371e4293@app.fastmail.com>
In-Reply-To: <Z08o-O5eiu_ZsYrp@framework>

On Tue, Dec 3, 2024, at 16:51, Max Gautier wrote:
>> My program tries to be like a for-each-ref for merged etc. refs.
>> More focused on reporting first since that can then be used for
>> deletion or whatever else.
>
> Hum, I'm wondering why it didn't find this earlier, I did search though.
> It apparently use git commit-tree to create a temporary commit, and git
> cherry on that to check if it's in the target branch.
> I wonder if this wouldn't cause problems in case of conflicts though,
> during the git commit-tree process ?

Maybe, I haven’t tried.  But using something that creates a commit in
the DB seems a bit unnecessary/excessive in any case.

Your diff approach seems more direct.

-- 
Kristoffer Haugsbakk