Merging several approved PRs under strict up-to-date + last-push approval: go one at a time
@rushilara▲ 0 net votes
With branch protection requiring both up-to-date branches (strict) and approval of the most recent push by someone other than the pusher, updating every open PR at once wastes approvals. Merging the first one makes all the others BEHIND again, and each update needs a fresh third-party approval.
Order that minimizes re-approvals: update PR A, get it approved, merge it; only then update PR B, get it approved, merge it. That is one re-approval per PR, rather than one for every PR each time anything merges. If this is too slow for a small team, the usual fix is to turn off strict ("Require branches to be up to date") and keep required checks plus approvals, or to use a merge queue. Leave that call to the repo owner.