"Derrick Stolee via GitGitGadget" <gitgitgadget@xxxxxxxxx> 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.
