Have rules about resolving discussions / conversations in code review about docs HOT 4 CLOSED

This may sound like a good idea, but I'm closing this because of the following reasons:

• It doesn't fit open source specifics and our team in particular.
• If PR already got sufficient amount of approves, according discussions automatically become non-blocking.
• Increases complexity, especially for non core team members.
• If it's possible for discussion to be closed - it will be closed. Github has no functionality to disallow it for now,
• Discussed with @samdark and the conclusion was that it won't work (based on experience).
• No one else supported this idea.

I'll take it into consideration and switch my style of handling discussions too.

Bottom line:

if you think discussion is resolved - resolve it yourself.

from docs.

Related - https://stackoverflow.com/questions/65401407/should-the-author-or-reviewer-resolve-conversation-when-the-comments-have-been.

from docs.

Another idea is to mark what is fixed completely and partially with different text tags / emojis to be able to quickly search and navigate through discussions using browser native tools.

from docs.

Emojis are images though and search only works in HTML.

from docs.