You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Spec Core Team often has the manual task of cleaning up comments that appear from contributors at the top-level of the MSC (a PR comment, rather than a PR review comment). Cleaning them up involves copying the contents of the comment, hiding it, then starting a new thread on the MSC (typically at line 1) and pasting the contents there as a quote. Along with some text to inform the user as to why it was necessary.
This is time-consuming manual work. And sometimes when we don't catch these comments quickly enough, other people will reply with another top-level comment, making the problem worse.
It would be nice if mscbot could take care of doing that automatically, along with a canned explanation. It should support a config option that excludes certain users (SCT, guardians, MSC author) who occasionally do need to post top-level from the correction.
The text was updated successfully, but these errors were encountered:
if possible, it'd be nice to hide the original comment rather than delete it (so notifications on github work properly). Also if the note to the author and copy/paste of the comment be in the same threaded comment, would be appreciated (to reduce the number of comments github needs to load).
The Spec Core Team often has the manual task of cleaning up comments that appear from contributors at the top-level of the MSC (a PR comment, rather than a PR review comment). Cleaning them up involves copying the contents of the comment, hiding it, then starting a new thread on the MSC (typically at line 1) and pasting the contents there as a quote. Along with some text to inform the user as to why it was necessary.
This is time-consuming manual work. And sometimes when we don't catch these comments quickly enough, other people will reply with another top-level comment, making the problem worse.
It would be nice if mscbot could take care of doing that automatically, along with a canned explanation. It should support a config option that excludes certain users (SCT, guardians, MSC author) who occasionally do need to post top-level from the correction.
The text was updated successfully, but these errors were encountered: