Re: --shallow-exclude=ref -> "ambiguous deepen-not" error

From: Ben Knoble <ben.knoble@gmail.com>
Date: Sep 16, 2025, 20:34 UTC
Message-ID: <7A5A29A3-3738-4BD6-ADB2-F3D1DE355B80@gmail.com>
In-Reply-To: <20250916175740.1044452-1-phahn-oss@avm.de>

Show 31 quoted lines

> Le 16 sept. 2025 à 13:59, Philipp Hahn <phahn-oss@avm.de> a écrit :
> 
> Hello Ben,
> 
> Thank you for your reply.
> 
>> On Tue, 16 Sep 2025 at 13:03:41 -0400 D. Ben Knoble <ben.knoble@gmail.com> wrote:
>>> On Tue, Sep 16, 2025 at 10:58 AM Philipp Hahn <phahn-oss@avm.de> wrote:
>>>                     A---B---C topic
>>>                    /
>>>               D---E---F---G master
> 
>> I might have misunderstood, but aren't the commits you're interested
>> in here the ones named by
>> 
>>    git rev-list master..topic
>> 
>> ?
> 
> Yes, which is I have described using `CI_MERGE_REQUEST_TARGET_BRANCH_NAME :=
> master`.
> 
> But as also described this fails for those "merged regsult pipelines", where GitLab creates a temporary merge "X" and then runs its pipeline on "X":
> 
>>                     A---B---C topic
>>                    /         \
>>                    /        __X temp
>>                    /       /
>>               D---E---F---G master
> 
> Here `master..temp` becomes just "X", but not "A-B-C".

Here you should still use master..topic if you want to lint each individual commit, plus include temp if you want to lint the merge.