mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-20 17:26:56 -05:00
Update docs/user/blocking-user.md (#677)
Spamming a repository is only meaningful in the issues. https://forgejo.codeberg.page/@docs_pull_677/docs/next/user/blocking-user/ Co-authored-by: Earl Warren <earl-warren@noreply.codeberg.org> Reviewed-on: https://codeberg.org/forgejo/docs/pulls/677 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: avobs <avobs@noreply.codeberg.org> Co-committed-by: avobs <avobs@noreply.codeberg.org>
This commit is contained in:
parent
7e60f058d1
commit
866d79d0fe
1 changed files with 1 additions and 1 deletions
|
@ -3,7 +3,7 @@ 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.
|
||||
Blocking another user is desirable if they are acting maliciously or are spamming your repository (for instance by adding unsolicited comments in issues). 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
|
||||
|
||||
|
|
Loading…
Reference in a new issue