Sequential Merge Strategy in Large-Scale Repository

Problem

Merging pull requests into large-scale repositories with hundreds of developers working together can be challenging. When a PR (pull request) is raised, CI checks run on top of it. As the git repository size increases, the number of pull requests will increase proportionally.

As an ideal case, we should always run CI with the base as the updated main (default) branch.

Assuming a pull request will take 10 minutes to pass CI, on a large-scale repo, it is almost …

base case developers git large merge pull requests repositories repository request requests run scale size strategy working