github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[Feature] Custom Reserved Usernames and patterns #3028

New Issue
Open
opened 2025-11-02 04:57:55 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:57:55 -06:00
Owner
Copy Link

Originally created by @mateusza on GitHub (Mar 8, 2019).

Currently, the list of invalid usernames and username patterns is defined in source code and compiled into Gitea.

There should be a configuration variable where one could place additional restrictions based on local requirements.

Description

...

Screenshots

Originally created by @mateusza on GitHub (Mar 8, 2019). Currently, the list of invalid usernames and username patterns is [defined in source code](https://github.com/go-gitea/gitea/blob/9fd8b2621fb6e25e5cce7a5b5b08a993a145bc78/models/user.go#L715) and compiled into Gitea. There should be a configuration variable where one could place additional restrictions based on local requirements. ## Description ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 04:57:55 -06:00
GiteaMirror commented 2025-11-02 04:57:56 -06:00
Author
Owner
Copy Link

@mateusza commented on GitHub (Mar 9, 2019):

Ideally gitea should be able to optionally run external command that would check the name according to any rules or by querying external sources, and exit with proper return value.

@mateusza commented on GitHub (Mar 9, 2019): Ideally gitea should be able to optionally run external command that would check the name according to any rules or by querying external sources, and exit with proper return value.
GiteaMirror commented 2025-11-02 04:57:56 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 16, 2019):

These reserved names should be stored on database and Admin UI could operate them.

@lunny commented on GitHub (Mar 16, 2019): These reserved names should be stored on database and Admin UI could operate them.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3028
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?