Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • gitlab-ce
  • Repository

Switch branch/tag
  • gitlab-ce
  • lib
  • tasks
  • gitlab
  • list_repos.rake
Find file BlameHistoryPermalink
  • Zeger-Jan van de Weg's avatar
    Gitlab::Shell works on shard name, not path · ec442366
    Zeger-Jan van de Weg authored Apr 13, 2018
    Direct disk access is done through Gitaly now, so the legacy path was
    deprecated. This path was used in Gitlab::Shell however. This required
    the refactoring in this commit.
    
    Added is the removal of direct path access on the project model, as that
    lookup wasn't needed anymore is most cases.
    
    Closes https://gitlab.com/gitlab-org/gitaly/issues/1111
    ec442366

Replace list_repos.rake

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7