Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitaly gitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 550
    • Issues 550
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 57
    • Merge requests 57
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitalygitaly
  • Issues
  • #1423
Closed
Open
Created Dec 07, 2018 by Jacob Vosmaer@jacobvosmaer-gitlabDeveloper

Explicitly disable auto gc on pool repositories

https://git-scm.com/docs/git-config#git-config-gcauto

Git will sometimes automatically run git gc. In GitLab we globally disable this with auto.gc=0 in Git config.

I think it's critical for object dedup that auto gc never runs in a pool repository because if the remotes are out of date that may lead to data loss. Considering that Gitaly does not own the global Git config, and because of the bad consequences if auto.gc gets set the wrong way, I think should consider explicitly setting gc.auto=0 in the local git config of pool repositories.

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