Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2687

Closed
Open
Created Jan 22, 2013 by Administrator@rootOwner

Gitlab forcing lowercase repo names

Created by: tbe

We just migrated a huge repository base from gitolite plain to gitlab. As gitlab forces lowercase names, and we have projects with mix-case names, the migration does break many configurations. Also we have the wired case, that we have two repositories only differing in some uppercase letters in the name. After the import, only the lowercase repository is available.

gitlab should allow the users to decide which way they name there repositories.

As unix file-systems ARE case sensitive, this behaviour could break thing in several ways, after importing repositories.

Assignee
Assign to
Time tracking