Ask HN: Strategy for Choosing PRs to Combine
Goal: validate PRs fast so release manager can approve them to close PR
Ask: rather than some Jenkins job taking PRs one at time for validation, need a strategy to pick several candidate PRs I can combine and validate together perhaps based on disjointedness of change set
My previous job had zillions of very small repos eg one task, lib. Here running PRs in order is effective, obvious. Each repo had an owner so changes were a bit more parallel. Of course it means building code is somewhat harder because dependencies must be found and combined. Dpkg helped a lot there
Monorepo is the opposite. All the code is in one trunk. It either builds and validates with PR or no. However, there's now more to build and validate and it's no longer obvious which PRs should be considered for a validation run. Sequential processing of today's PRs could run into tomorrow creating an ever increasing backlog.
I want to focus on PR selection. Making the validation faster say through bazel which can better exclude sub validation steps for files that haven't changed, is something we will do regardless