When a PR is merged into master, our automation creates a new PR from master --> release/X for each release branch in the repo. The approver assigned is the person who merged the PR into master.
Instead, the PR from master --> release/X should be assigned to the person who submitted the PR into master originally. The reason for this is twofold:
The submitter has context for the change (which is especially useful when there's a merge conflict)
It's less work for the reviewer of the original PR
When a PR is merged into
master
, our automation creates a new PR frommaster
-->release/X
for each release branch in the repo. The approver assigned is the person who merged the PR intomaster
.Instead, the PR from
master
-->release/X
should be assigned to the person who submitted the PR intomaster
originally. The reason for this is twofold: