Tell us it is wrong
This marks other people's work, so being correctable matters more than being right. Every deduction names the file it came from, which means a disagreement can always be settled by looking rather than arguing.
A mark is wrong
The most useful thing you can send. The rubric misses things, particularly outside JavaScript and Python, and every miss is a rule somebody can fix.
Every report page has a link that opens an issue already filled in with the repository, its mark, and its weakest category. Use that one if you are looking at a report, because it saves you writing any of it out.
What helps most: which check was wrong, and the file or setting it failed to find. The rules live in src/grade and each one is a small pure function, so a pull request is usually a handful of lines.
Something is broken
A page that will not load, a repository that will not mark, a badge stuck on an old score.
Include the URL. If a mark looks stale, add ?refresh=1 to
the report URL first, which forces a re-mark and fixes it more often than not.
Everything else
Ideas, disagreements with the whole premise, or a repository you think should be on the class list.
@dejansto_ or a discussion.
Requests to remove a public repository from the class list are always honoured, no reason needed. Ask either way.
What we will not argue about
Whether a low mark means bad code. It does not, and the site says so. It means an agent will waste turns, which is a different claim.
Whether the scheme should exist. Reasonable people disagree, and that is a conversation for a thread rather than an issue. Individual rules are where the useful argument lives.