Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hgitaly hgitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • 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
  • #85

Closed
Open
Created Oct 13, 2021 by Georges Racinet@gracinet🦑Owner

RepositoryService: implement Cleanup

This is not a rewrapping of git clean. Rather, this relies on git worktree remove and git worktree prune. These are similar to the temporary working directories we're using on the server side with hg share. See man git-worktree for more information.

This method is low priority because:

  • our Mercurial shares are automatically removed after use (but we could later on reuse them with a pool for performance reasons on large repositories). Also their creation is currently entirely managed from the Rails app, so it would be consistent to perform any cleanup of them from the same place, namely HgGitRepository.
  • Git::Repository rescues the call if it fails
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking