New release: Block users directly from security advisories

[moraesc]

Maintainers need more tools to keep their communities healthy, especially as spam, abuse, and other unwanted noise increasingly affect collaborative spaces.

We recently added the ability for owners of personal repositories to block users from Issue and pull request comments, building on functionality already available in organization-owned repositories. Today, we’re extending that moderation capability to security advisories in public repositories owned by both organizations and personal accounts. Security advisories are an important collaborative surface and an increasingly common source of spam.

With this update, you can:

• Block a user directly from a security advisory description or comment using the three-dot menu.
• Review a confirmation explaining what blocking the user means before taking action.
• Keep the security advisory available while removing the source of spam or abuse.
• In organization-owned repositories, organization moderators and administrators can initiate a block. In personal repositories, the account owner can do so.

We hope this gives maintainers more convenient, consistent tools for managing their communities without leaving the page. Let us know how this update is helping you with moderation and if there are any other tools you're looking for the keep your communities healthy.

[zarif501]

🛡️ Security Advisory Moderation
GitHub has expanded its moderation capabilities to help maintainers combat spam and abuse. Building on the existing ability to block users from Issues and Pull Requests, you can now block disruptive users directly within security advisories on public repositories.
✨ Key Features
With this update, you can now:
Block directly: Initiate a block straight from a security advisory description or a specific comment by clicking the three-dot menu.
Review before action: View a confirmation screen that explains exactly what blocking the user entails before you finalize the decision.
Preserve content: Keep the important security advisory active and visible to the community while successfully removing the source of the noise or abuse.
👤 Who Can Initiate a Block?
The ability to use this moderation tool depends on the repository type:
Organization-Owned Repositories: Organization administrators and designated moderators.
Personal Repositories: The individual account owner.

[iawaisahmd]

one useful next step would be giving maintainers an option to report and block in the same action, especially for repeated spam across multiple security advisories. some visibility into whether a blocked account has interacted with other advisories in the repository would also help maintainers clean up coordinated spam faster.