But then are you looking at the git context of all the comments you come across ? I'd argue you could do the same on methods and class you want more context on

But then are you looking at the git context of all the comments you come across ? I'd argue you could do the same on methods and class you want more context on, removing the need for the majority of comments, and most companies will have the associated ticket numbers or design discussions attached to the MR/PR. I think there will still be rare situations where comments are absolutely needed, but in these rare cases they should probably refer to an external resource (a bug report for a specific library, an incident that required a specific fix, etc.)