Users (who aren't whitelisted) who post top-level to an proposal should have their comment automatically moved to a PR review comment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No file, test, or entry point is named in the issue. Start by locating the code that handles GitHub pull-request comments and configuration, then trace how top-level comments and user exclusions are represented. Done means eligible comments are moved into review threads with the canned explanation while excluded users are unaffected.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from matrix-org/mscbot-python
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
matrix-org/mscbot-python#39 ·
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matrix-org/mscbot-python#38 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
matrix-org/mscbot-python#36 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
matrix-org/mscbot-python#35 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
matrix-org/mscbot-python#34 ·
All issues in matrix-org/mscbot-python
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100