Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 818
    • Issues 818
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #992

Closed
Open
Created Jul 22, 2011 by Bitbucket Importer@bitbucket_importerOwner

Awkward behavior of the "default" group in repo registry

Created originally on Bitbucket by bozr

The default group cannot be removed from the repo registry. Is this because there should at least be one group available?

The current behavior is quite awkward:

I have a bunch of repos each inside a group. I also renamed the default group to something of my liking. So, now it's not obvious which group is the former default group. Apparently thg still remembers this, because sometimes I remove a repo group from the registry, however with the former default group the remove option is not available from the drop down menu.

IMHO it would be much nicer to prevent the user from deleting the last group if there is such a requirement.

I'm using TortoiseHg 2.1.1

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking