Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mercurial_keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • mercurial_keyring
  • Issues
  • #3

Closed
Open
Created Jul 05, 2010 by Bitbucket Importer@bitbucket_importerOwner

Can not use mercurial_keyring with sub repository

Created originally on Bitbucket by chen.hendrawan

When the repo contain sub repositories, mercurial keyring refuse to work.

{{{ d:\Temp\temp-sandbox\sandbox>hg push pushing to http://myuser@myurl.domain.com/hg/main/ pushing subrepo SourceCode-SubRepo1 to http://myurl.domain.com/hg/subrepo1 Username not specified in .hg/hgrc. Keyring will not be used. http authorization required realm: domain.com }}}

I can't put the username in hgsub file since it is shared. I've tried to add {{{ SourceCode-SubRepo1 = http://myuser@myurl.domain.com/hg/subrepo1 }}} into hgrc with no effect.

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