mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-28 18:42:51 -05:00
9af05bfb01
Reviewed-on: https://codeberg.org/forgejo/website/pulls/323 # Conflicts: # v1.19/admin/command-line.md # v1.19/admin/config-cheat-sheet.md # v1.19/admin/database-preparation.md # v1.19/admin/email-setup.md # v1.19/admin/incoming-email.md # v1.19/admin/index.md # v1.19/admin/logging-documentation.md # v1.19/admin/reverse-proxy.md # v1.19/admin/seek-assistance.md # v1.19/admin/upgrade.md # v1.19/developer/code-forgejo-org.md # v1.19/developer/index.md # v1.19/index.md # v1.19/license.md # v1.19/user/agit-support.md # v1.19/user/api-usage.md # v1.19/user/authentication.md # v1.19/user/email-settings.md # v1.19/user/first-repository.md # v1.19/user/index.md # v1.19/user/issue-pull-request-templates.md # v1.19/user/issue-tracking-basics.md # v1.19/user/labels.md # v1.19/user/linked-references.md # v1.19/user/merge-message-templates.md # v1.19/user/oauth2-provider.md # v1.19/user/packages/cargo.md # v1.19/user/packages/chef.md # v1.19/user/packages/composer.md # v1.19/user/packages/conan.md # v1.19/user/packages/conda.md # v1.19/user/packages/container.md # v1.19/user/packages/generic.md # v1.19/user/packages/helm.md # v1.19/user/packages/index.md # v1.19/user/packages/maven.md # v1.19/user/packages/npm.md # v1.19/user/packages/nuget.md # v1.19/user/packages/pub.md # v1.19/user/packages/pypi.md # v1.19/user/packages/rubygems.md # v1.19/user/packages/storage.md # v1.19/user/packages/vagrant.md # v1.19/user/project.md # v1.19/user/protection.md # v1.19/user/push-options.md # v1.19/user/push-to-create.md # v1.19/user/repo-permissions.md # v1.19/user/webhooks.md # v1.19/user/wiki.md # v1.20/user/semver.md
50 lines
2.2 KiB
Markdown
50 lines
2.2 KiB
Markdown
---
|
|
title: Blocking a user
|
|
license: 'CC-BY-SA-4.0'
|
|
---
|
|
|
|
Blocking another user is desirable if they are acting maliciously or are spamming your repository. For such cases, Forgejo provides the functionality to block other users. When you block a user, Forgejo does not explicitly notify them, but they may learn through an interaction with you that is blocked.
|
|
|
|
## How to block someone
|
|
|
|
In order to block another user, go to their profile page and click on the "Block" button.
|
|
|
|
|
|
|
|
A popup will show; please read carefully what blocking another user implies, and if you accept the implications, click on Yes.
|
|
|
|
|
|
|
|
## How to block someone as an organization
|
|
|
|
It is possible to block a user from an organization, this has the same implications as a normal user blocking another user. To block a user from an organization, you must be on that organization's Owners team.
|
|
|
|
Navigate to your organization's settings and select the Blocked Users page.
|
|
|
|
|
|
|
|
Find the person you want to block in the search bar, select the user and click block.
|
|
|
|
|
|
|
|
You will now see the blocked users in the list, along with the date they were blocked.
|
|
|
|
|
|
|
|
To unblock that person, you can click the unblock button next to their name.
|
|
|
|
|
|
|
|
## Implications of blocking a user
|
|
|
|
When you block a user:
|
|
|
|
- You stop following them.
|
|
- They stop following you.
|
|
|
|
After you've blocked them:
|
|
|
|
- They cannot cause any notifications for you anymore by mentioning you.
|
|
- They cannot open issues or pull requests on repository you own.
|
|
- They cannot add reactions to your comments.
|
|
- They cannot post comments on issues and pull request you've opened.
|