-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add user blocking #29028
Add user blocking #29028
Conversation
Co-authored-by: Lauris BH <lauris@nix.lv>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you missed a migration for the new table.
These are all more or less related to the new htmx code. Nothing I can/will fix in this PR.
I added a specific error message here new but the "edit content" code does not handle errors, so it's not getting displayed (still nothing I can fix in this PR). To prevent these missing UI errors I could hide the specific elements, so a user can't really access them in the first place. |
I will fix whatever htmx problems happen, just open an issue and mention (@) me |
…into feature-user-block
@KN4CK3R Could you resolve conflicts? |
* giteaofficial/main: Document that all unmerged feature PRs will be moved to next milestone when the feature freeze time comes (go-gitea#29578) Make admin pages wider because of left sidebar added and some tables become too narrow (go-gitea#29581) Refactor star/watch button (go-gitea#29576) Remove unnecessary SanitizeHTML from code (go-gitea#29575) Add missing database transaction for new issue (go-gitea#29490) Fix incorrect package link method calls in templates (go-gitea#29580) Move some asymkey functions to service layer (go-gitea#28894) Add user blocking (go-gitea#29028) # Conflicts: # templates/repo/issue/view_content/context_menu.tmpl
Fixes #17453
This PR adds the abbility to block a user from a personal account or organization to restrict how the blocked user can interact with the blocker. The docs explain what's the consequence of blocking a user.
Screenshots: