Block users directly from security advisories
Summary
You can now block a user directly from a security advisory page in public repositories owned by either an organization or a personal account. This brings the streamlined moderation experience… The post Block users directly from security advisories appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> You can now block a user directly from a security advisory page in public repositories owned by either an organization or a personal account. This brings the streamlined moderation experience available for issues and pull requests to security advisories.
Security advisories contain user-created content and, like other collaborative surfaces, can attract spam or abuse. Previously, addressing this required navigating to organization settings, personal settings, or the user’s profile.
With this update, you can:
Block a user from the three-dot menu in a security advisory description or comment without leaving the page.
Review a clear confirmation of what blocking the user means before taking action.
Keep the security advisory intact while removing the source of spam or abuse.
In organization-owned repositories, only organization moderators or administrators can initiate a block. In personal account-owned repositories, the account owner can initiate a block.
Join the Community discussion to share your questions or feedback.
The post Block users directly from security advisories appeared first on The GitHub Blog.
Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.