Feature Request: make inline comment "sticky" across changed lines

[yuanchen-zhu]

Select Topic Area

General

Body

During code review, a fundamental workflow involves the following:

• The reviewer makes an inline comments suggesting some changes
• The author modifies the relevant lines per the suggestions
• During the next round of review, the reviewer checks that the suggestions have been addressed. For the majority of small suggestions, that involves looking at roughly the same region of code around the lines where the original inline comments have been made.

Right now, Github UI has the following 2 issues.

• If a line is changed, then the original inline comment will no longer show up in the "Files changed" tab. It would help developer efficiency greatly if Github makes a best-of-effort attempt to locate the lines in the newer files where the original inline comments should stick to. (Phabricator does a great job doing this. Github should just copy it)
• In the conversation view, where the inline comments made during a code review are collected, it would greatly help developer efficiency if the latest version of the code around the original inline comments are shown, alongside the original code.

Because of the lack of these two features, right now when I want to check that an inline comment has been addressed, I need to manually navigate to the corresponding file and the approximate line number, and read the block of code in the latest checked out PR.

This feature request is basically the same request implied here (https://github.com/orgs/community/discussions/23138), but since that post was in the "New to GitHub" category, GitHub employees no longer seem to look at it. Hence I'm posting a new feature request here.

[gabmis]

100% Agree, I am currently forced to open two windows side-by-side, one on the conversation tab and the other on the files changed tab. Only then, am I able to somewhat efficiently check that my comments have been addressed correctly. Please implement this. There were hundreds of upvotes in the thread from 2019. 🙏 ❤️

[simon-knu]

It's the main reason of why I don't want to switch from Azure DevOps to GitHub

The review of PR, especially from new or junior devs, is a nightmare

I think the DevOps system is prefect, it's a pity that we don't have this very basic feature

[Caitlin-Syntax]

This issue is now documented in at least four places with no real official response. GitHub, please, we're begging you. Fix this!

• https://github.com/orgs/community/discussions/9956
• https://github.com/orgs/community/discussions/17481
• https://github.com/orgs/community/discussions/23138
• https://github.com/orgs/community/discussions/110796 (this feature request)

[skillmaker-dev]

It's unprofessional seeing GitHub hasn't made any interaction with all the 4 discussions that have been requesting this feature for at least 5 years, it makes the review annoying and makes you think of going back to Azure DevOps, Gitlab, or Bitbucket.
Come on Github team do something about it!