#@Shadow How can I help triage issues,

1 messages · Page 1 of 1 (latest)

delicate bobcat
halcyon mossBOT
#

Br00tal ask. Here’s the fastest, highest‑impact path (low time):

Spam:

  • Click the “⋯” on the spam comment → Report content (goes to GitHub trust/safety).
  • Grab the issue/comment URLs and drop them here (or #clawdributors). We’ll nuke + block the account at org level.

Triage (when you’re already there):

  • Confirm if it’s a duplicate; link the canonical issue.
  • Ask for missing basics: repro steps, version/commit, logs, screenshots.
  • If it’s clearly invalid/unsupported, say so politely.

If you want, paste a short list of spammy issues/comments and we’ll clean house.

old cradleBOT
#

Br00tal question. You can help without perms:

For spam:

  • On the spam comment (⋯ menu) → Report content. Same on the issue itself.
  • On the spammer’s profile → Report abuse.
  • Drop the link here (or in a triage thread) and we can delete/block faster.

For triage (low-time, high-impact):

  • Confirm/repro: “reproduced on vX / can’t repro on vY”.
  • Link duplicates: “looks like #123”.
  • Add missing details: logs, OS, versions, steps.

If you want, I can give you a 30‑second “triage checklist” you can paste when you’re already in an issue.

delicate bobcat
halcyon mossBOT
#

Got it. If “Report content” isn’t showing, use one of these:

And drop the issue/comment links here (or #clawdributors). Maintainers can hide the comments + block the account at org level.

old cradleBOT
#

Got it. If the ⋯ menu has no “Report content”, use the abuse form directly:

Report spam (works even without repo perms):

  1. Copy the permalink to the spam comment (click the timestamp).
  2. Open: https://github.com/contact/report-abuse?report=spam
  3. Paste the comment/issue URLs + the spammer’s profile URL.

Also: open the spammer’s profile → Report abuse (top‑right menu).

Drop the URLs here too and we’ll block the account at org level.

tired timber
#

not sure if instructive but this is great , gonna try it a bit 🙂