From: Derrick Stolee <stolee@gmail.com>
Date: Tue, 20 Aug 2024 01:33:50 GMT
Subject: Re: [PATCH v3 0/4] git for-each-ref: is-base atom and base branches
Message-ID: <be1182e5-5b0d-4deb-8b47-e38d05d184a0@gmail.com>
In-Reply-To: <xmqqed6ke1dx.fsf@gitster.g>

On 8/19/24 3:52 PM, Junio C Hamano wrote:
> "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 
>> There are benefits to users both on client-side and server-side. In an
>> internal monorepo, this base branch detection algorithm is used to determine
>> a long-lived branch based on the HEAD commit, mapping to a group within the
>> organizational structure of the repository, which determines a set of
>> projects that the user will likely need to build; this leads to
>> automatically selecting an initial sparse-checkout definition based on the
>> build dependencies required. An upcoming feature in Azure Repos will use
>> this algorithm to automatically create a pull request against the correct
>> target branch, reducing user pain from needing to select a different branch
>> after a large commit diff is rendered against the default branch. This atom
>> unlocks that ability for Git hosting services that use Git in their backend.
> 
> Thanks for an update.  This iteration looks good to me.

Thank you for your careful review.

-Stolee