Open PR A-->main, while it's getting reviewed (or maybe it's in WIP state for some reason), create a branch B off A, and eventually open PR B-->A. Now, you never actually merge B-->A, it's only there so that the PR can be reviewed and diff can be seen. Can be repeated as needed.
In fact, IIRC, in the example above, if you merge PR A, GitHub will switch PR B's target branch to whatever A was merged to (in this case, main).