1.8 KiB
1.8 KiB
Reserved project and group names
Not all project & group names are allowed because they would conflict with existing routes used by GitLab.
For a list of words that are not allowed to be used as group or project names, see the
path_regex.rb file under the TOP_LEVEL_ROUTES, PROJECT_WILDCARD_ROUTES and GROUP_ROUTES lists:
TOP_LEVEL_ROUTES: are names that are reserved as usernames or top level groupsPROJECT_WILDCARD_ROUTES: are names that are reserved for child groups or projects.GROUP_ROUTES: are names that are reserved for all groups or projects.
Reserved project names
It is currently not possible to create a project with the following names:
- -
- badges
- blame
- blob
- builds
- commits
- create
- create_dir
- edit
- environments/folders
- files
- find_file
- gitlab-lfs/objects
- info/lfs/objects
- new
- preview
- raw
- refs
- tree
- update
- wikis
Reserved group names
Currently the following names are reserved as top level groups:
- 503.html
- -
- .well-known
- 404.html
- 422.html
- 500.html
- 502.html
- abuse_reports
- admin
- api
- apple-touch-icon-precomposed.png
- apple-touch-icon.png
- files
- assets
- autocomplete
- ci
- dashboard
- deploy.html
- explore
- favicon.ico
- favicon.png
- groups
- health_check
- help
- import
- invites
- jwt
- notification_settings
- oauth
- profile
- projects
- public
- robots.txt
- s
- search
- sent_notifications
- slash-command-logo.png
- snippets
- u
- unicorn_test
- unsubscribes
- uploads
- users
- v2
These group names are unavailable as subgroup names:
- -
- activity
- analytics
- audit_events
- avatar
- edit
- group_members
- hooks
- issues
- labels
- ldap
- ldap_group_links
- merge_requests
- milestones
- notification_setting
- pipeline_quota
- projects
- subgroups