Pin an individual comment from an issue

[hwittenborn]

Select Topic Area

General

Body

Currently you can pin GitHub issues, but not individual comments within those issues. It'd be helpful if I could pin an individual comment so that a helpful comment, such as a fix to an issue that's still being fixed, can be easily found within a comment.

I'm thinking the pinned comment can just be seen when viewing the issue directly - pinned issues can function as they currently do, and then the pinned comment can just be seen once the issue is clicked.

[cwway]

Chiming in on this - when using issues over time like a product dev/feature request catalogue, comments are added and stack up significantly.

The ability to PIN a particular comment, or perhaps overwrite ordering by assigning 1-2-3 priority, would be fantastic to bring at least one over-arching or conclusive comment to the top

[zadjii-msft]

Just to x-ref:

• Pin an individual comment from an issue #47912
• Add ability to pin comments in really long issue threads #27522
• Pin top / relevant comments #18523

all seem like they're the same request.

[Marcono1234]

And also from the now archived isaacs/github repository: isaacs/github#1008
Which contains some examples and references to related feature requests.

[gnowland]

And isaacs/github#1555 from the now archived isaacs/github repository.

[Marcono1234]

That issue from the isaacs/github repository seems to be about comments on PRs. For that there are other also other related suggestions here:

• Open commit suggestions are put into "hidden conversations" while resolved are presented #11842
• No way to easily view all unresolved conversations #7638

Though maybe having the option to pin comments on PRs could be useful nonetheless, but I am not sure if it would solve the issues mentioned in those discussions.

[gnowland]

The biggest issue here is when an important "current progress/blockers" comment gets hidden under "Load more..." leading to people constantly asking the current state. Pinning a comment should highlight it in some way as well as prevent it from being collapsed.

Heck, it might even make sense to collapse everything *up to* the pinned comment, since that comment is often the new jumping off point for further discussion on long-open issues.

[oleg-rswll]

This would be a really useful feature to have. Is there any status on when it may be available?

[Joao-Pedro-P-Holanda]

This feature of pinning comments can also be useful inside discussions, that naturally have more interactions than most issues. In a long term discussion (e.g. a discussion to keep track of the translation of a project's documentation) is important to have a way to keep the most relevant decisions or guidelines at the top.

[fantasai]

Came here to ask even if we could just mark or highlight certain comments as key comments. Sometimes there's multiple of these. But they get lost in long discussions, and can even be hidden under "load more".

Here's an example: w3c/csswg-drafts#6245 (comment) This comment is actually a good candidate for @gnowland's "collapse up until pin" idea, since it resets the conversation. But in many issues there are multiple key points that anyone working on the issue should review, and it's good to not lose those, either. In this issue we actually thought we had solved it until we went back and reviewed key comments in the discussion, which prompted redesigning the whole thing.

[alinnert]

This issue is another example. All of the sudden many JS framework dev servers print a warning in the terminal that something is making a request to the URL /.well-known/appspecific/com.chrome.devtools.json but it results in a 404. Everyone was confused, people thought some installed extension is responsible for this request.

Right in the middle of this conversation there is the answer to why this happens: The Chrome DevTools team added the feature "Automatic Workspace Folders" which is sending this request for any dev server on localhost to provide information about the current project. This changes the context of this issue completely. But, of course, it took me a while to find it.

And this is not the first time I've run into this kind of situation.