How can I see review comments together with the resulting code changes?

[LouisStrous]

Select Topic Area

Question

Body

The author made new code changes (in several commits) after I provided review comments on the old code changes. I would like to see in a single view the newest code changes and the (unresolved) review comments that spurred them, so I can most easily tell if and how the new code changes relate to the review comments, and can mark the comments as resolved if they have in fact been resolved. How can I arrange that?

In the "Conversations" view of the pull request I can see the review comments (most if not all of them marked as "Outdated") and the snippets of old code that they are associated with, but not the new code changes. In the "Files changed" view I can see before and after states related to the new code changes but then the review comments that led to the code changes aren't visible.

I can of course open two GitHub windows, one that shows the old comments and one that shows the new code changes, but then I have to manually find the corresponding items in both views, which is tedious and seems unnecessary because GitHub has all necessary information to perform that task for me and show the results in a single view.

[aflacake]

You can also link in the comments if you want to see the conversation in the old code.
In commit > to comment > select the conversation and copy the link

[LouisStrous]

Thank you for the quick response. Sorry, I don't recognize "commit > to comment". Is that for GitHub Desktop? I'm using GitHub via a web interface. I don't know by how much (if any) the web interface differs from the desktop application interface. I can copy a link to a conversation but then it is still me who's doing the work of figuring out where in the new code changes I should insert the link in a comment, and I suspect that following that link then leads me to the old code, so then I'm still not seeing the comment and the new code changes together. Or am I misunderstanding your suggestion?

[aflacake]

This is also on the web, I am also a smartphone user (especially).
You cant view changes simultaneously, GitHub doesn't provide this feature. But I gave a solution that "takes you" in the previous commit conversation history.

Before you merge an author pull request, old changes are merged with new changes. So that takes you to the repo she/he forked to see in more detail where the changes are:

I suggest looking at the change history via author's repo forked commits:
In the repo > to the commit **above the file (history clock image)

[LouisStrous]

Thank you for confirming that GitHub cannot simultaneously show code changes with the review comments that prompted those code changes. I'll mark that as the answer, but it isn't the answer I was hoping for. I'm very surprised about the lack of this feature; it seems very desirable to me, and it isn't obvious to me why it should be difficult to provide. One way in which it could be done is to display a three-way comparison, as is common for resolving merge conflicts. The "A" version could be the base commit of the previous review. The "B" version could be the last commit included in the previous review, which is equal to the base version of the latest changes. And the "C" version could be the most recent commit. The "A" and "B" versions could have the (unresolved) review comments in them, as in the "Conversations" view.

[aflacake]

You're welcome, I give the answer that I know. It's good if you request a feature for this, I also agree because at first I was confused about where I had requested a pull then when I asked for a pull again it made it one with the previous pull request.

[LouisStrous]

I've created https://github.com/orgs/community/discussions/152465 for this. I don't know how else to post a feature request.

[aflacake]

Good! I also hope that other users provide the opinions proposed, and I.