P4 Description
If you use dependent PRs, and integrate the first one (the one without a dependency), then the diff of the second PR will show the contents of both PRs.
This is fine if all you're going to do is to integrate the second PR, but if you want to continue the review process, then this will be very confusing for the reviewers.
To solve this, the PR owner can merge the master branch into the branch of the second PR. After that, the diff will look correct again.
I think it would be good if the bots could inject some kind of warning / help message about this when a dependent PR is integrated.
This is fine if all you're going to do is to integrate the second PR, but if you want to continue the review process, then this will be very confusing for the reviewers.
To solve this, the PR owner can merge the master branch into the branch of the second PR. After that, the diff will look correct again.
I think it would be good if the bots could inject some kind of warning / help message about this when a dependent PR is integrated.
