Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hgitaly hgitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • hgitalyhgitaly
  • Issues
  • #73
Closed
Open
Created Sep 07, 2021 by Georges Racinet@gracinet🦑Owner

BlobsService: implement ListBlobs and ListAllBlobs

These new methods in Gitaly 14.2 are documented in blob.proto.

On the Rails side, as of 14.2.0, only ListBlobs is exposed in Gitlab::Git::Repository#blobs, and the main current use case is to be a new backing for size limits of push operations in GitAccess (was previously using RefService.ListNewBlobs). This access control is not relevant for Mercurial anyway, because content is received in one step from the point of view of the Rails app (in Git, commits are received first, and only then references get updated, allowing to do more checking between both).

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