What blocking changes, and what it does not
Blocking is a moderation tool for your own account, not a security boundary. It does not turn a public repository private, and it does not remove anything already indexed or copied elsewhere on the public web. Treat it as a way to cut ties and limit interactions, not as access control or erasure.
Blocking a GitHub user removes following and collaborator relationships and restricts interactions in repositories you own. Source
The blocked user is not notified, and the thread history stays intact. Blocking from a comment is a moderation action, not a deletion action.
GitHub does not notify the user when blocked; blocking from a comment does not delete the original issue, pull request, discussion or advisory. Source
Shared-space limits and content removal
Blocking is not a blanket silence. Shared organizations, public threads and other common spaces can still show that user’s activity. The blocked user can also delete their own existing content, which may leave gaps in a thread you were relying on.
You may still see a blocked user’s activity in shared spaces, and they can delete their existing content. Source
Before-action checklist for collaboration consequences
Use this checklist before you block a collaborator, because the change is easier to make than to unwind.
- Confirm whether the person is a collaborator on any repository you own; blocking removes that relationship.
- Identify open issues, pull requests, discussions or advisories where they are the author or a participant, and note that these are not deleted by blocking.
- Check shared organizations and public threads where their activity may still appear.
- Decide whether you need to preserve their existing comments for context before they can delete them.
- Record the reason and date for your own audit trail; GitHub does not notify the user.
Decision table: is blocking the right tool?
| Goal | Does blocking help? | Better fit |
|---|---|---|
| Stop a user following you or collaborating on your repos | Yes | Block |
| Limit interactions in repositories you own | Yes | Block |
| Prevent access to a private repository | No | Repository access settings |
| Remove a public issue, pull request or advisory | No | Edit or close the thread |
| Erase public-web copies or search results | No | Platform and search removal processes |
| Silence activity in shared organizations | No | Organization-level moderation |
Manual verification checklist
After blocking, verify the change yourself rather than assuming it worked:
- Open your followers and following lists and confirm the relationship is gone.
- Check each repository you own for collaborator status.
- Reopen the issue, pull request, discussion or advisory you blocked from and confirm it still exists.
- Review shared organization activity to see whether the user still appears.
- Note any comments the user deleted after the block, since those gaps are not restored by unblocking.
A username search is a lead, not proof of ownership. TraceSeek can optionally check known public usernames across 3,000+ platforms in a 20-30 second scan, with a free first scan; it cannot change platform settings, access private content, prove ownership, or find all accounts by phone or email. For account-audit steps that pair with this moderation decision, see our account-audit guidance and methodology notes.
Key facts
- Blocking a GitHub user removes following and collaborator relationships and restricts interactions in repositories you own.
- GitHub does not notify the user when blocked.
- Blocking from a comment does not delete the original issue, pull request, discussion or advisory.
- You may still see a blocked user’s activity in shared spaces, and they can delete their existing content.
- Blocking is a moderation action for your own account, not private-repository access control or public-web erasure.