fwiw, that problem is actually really just a symptom of deeper architectural debt: • velocity should be high enough that PRs don't back up • code bases should avoid structure/patterns that force developers to have 'interacting changes' (i.e. when php has a singular 'routes.php' and thus if 5 people need to change paths in an api, they create 5 conflicting/tangled changes) • file structure should assist testing/ci so that a single change would only trigger relevant tasks, rather than 'the full CI suite' so really, the pattern should be: • adjust the architecture to avoid this some languages make this easier to do than others, to be frank.

First class feature of GitHub