Point issue/PR linkbacks to exact comment that caused the linkback

Issue events like someone mentioned this issue usually links to the issue directly. But it would be helpful if the link was to the mention specifically; i.e., append the link with the #issuecomment-<eventID> link so that clicking on the mention event will take the user directly to the comment it was referenced in. Especially, when the linked issue is hundreds of comments long ( example reference link ) .

There are multiple problems that I can think of :

1. Whether there is an API to fetch all the issue events
2. Even if there was an API, does it have the event IDs required

I looked around the Issues REST API documentation, but couldn’t find something that was suitable for this purpose. I did not go through the graphQL API since it is too confusing for me to comprehend.

Assuming that the above problems do not exist, another problem is that there is only one mention event per link; i.e., even if you mention the same issue multiple times ( in different comments ) from the another issue, there will not be duplicate mention events. That raises the following questions :

1. do the event contain all the references to the issue or only the first reference?
2. if it does contain all the references, then which reference should the proposed feature link to?

Does all of this seem like a technically challenging feature? Is this a feature that would be feasible for Refined GitHub?

[fregante]

I meant find it on the linked issue. In short:

1. User visit issue
2. User sees linkback on current issue
3. Use clicks on linkback, which has no hash
4. Page starts loading
5. Refined GitHub looks for a link to the previous page
6. Refined GitHub changes the hash to that comment, if found

This feature would be split in 2 parts:

• on one load, it finds linkbacks and appends something like #from-sindre/refined-123 which is just a reference to the current page and it doesn’t actually work on its own
• on another load, if the above hash is present, it looks for comments that include a link to sindre/refined/issue|pull/123 and sets location.hash.replace('#issuecomment-1356743') to focus the comment

This requires no API calls.

Does it make more sense now? Am I getting this right?

As for commit links, they’re simply not handled, we could easily exclude them.

[fregante]

We can give this feature a try