個人リポジトリのコメントからユーザーをブロック可能にBlock users from comments in personal repositories

GitHub has added a way for people who own repositories under personal accounts to block or unblock other users straight from the comment threads on pull requests and issues. According to the company's changelog, the option now sits alongside individual comments in those threads, giving maintainers a faster path to shut down unwanted or disruptive exchanges as they happen.

The workflow matters because moderating a project has historically meant breaking your concentration. To block someone, a repository owner typically had to open the offending user's profile page or dig into account settings, confirm the action, and only afterward return to the discussion. By surfacing block and unblock controls at the point of the comment itself, GitHub reduces that friction and lets an owner respond to spam, harassment, or off-topic noise without navigating away.

Blocking on GitHub is an established account-level feature rather than a new concept. When a personal account blocks another user, that person is generally prevented from interacting with the blocker's content, including commenting, opening issues or pull requests, and adding reactions. The change described in the changelog appears to be about where and how the action can be triggered, rather than altering what blocking does once it takes effect. The ability to unblock from the same place is a useful complement, since moderation decisions are sometimes reversed.

It is worth noting the distinction between personal repositories and those owned by organizations. Organization owners and moderators have had a broader set of moderation controls for some time, including the ability to block users at the organization level. Bringing comment-level blocking to repositories owned by personal accounts helps narrow that gap, giving solo maintainers and small projects tooling closer to what larger teams already use. That is meaningful because a large share of open source work is carried out by individuals maintaining projects under their own usernames rather than under an organization.

Comment-level blocking fits into a wider collection of moderation features GitHub has built over the years. Maintainers can already lock conversations to stop further replies, hide individual comments while keeping them on the record, set temporary interaction limits that restrict who can comment during a heated period, and report abusive behavior to GitHub itself. Repositories can also publish a code of conduct and contributing guidelines to set expectations up front. Blocking from a comment slots in as another lightweight, immediate tool rather than a replacement for those heavier measures.

The context here is the ongoing challenge of harassment and spam in public software development. Open source maintainers, many of whom volunteer their time, are frequent targets of hostile comments, drive-by demands, and automated spam on their issue trackers. Reducing the number of steps required to remove a bad actor from a thread is a modest quality-of-life improvement, but it can matter in the moment when a maintainer is trying to keep a discussion productive. It also lowers the chance that someone abandons a moderation action simply because the process was cumbersome.

For developers who want to try it, the feature is accessed from the comment interface on issues and pull requests within repositories they own under a personal account. The changelog frames the steps as opening the relevant menu on a comment and choosing to block or unblock the author, though the exact controls may vary slightly by interface. As with other changelog entries, GitHub typically rolls such changes out to the web experience first, and the behavior of previously configured blocks is unlikely to change.

The update is incremental rather than transformative, and GitHub has not tied it to any pricing change or premium tier based on the information provided. Still, for the many individuals who run repositories on their own, having block and unblock available inline is a sensible refinement that aligns personal-account moderation more closely with the controls organizations have offered. Maintainers who deal with recurring unwanted interactions are the most likely to feel the benefit, and the addition reflects GitHub's steady, incremental approach to giving repository owners more direct control over the conversations happening on their projects.