git-maintenance - Run tasks to optimize Git repository data
git maintenance run [<options>]
Run tasks to optimize Git repository data, speeding up other Git commands and reducing storage requirements for the repository.
Git commands that add repository data, such as
git add or
git fetch, are optimized for a responsive user experience. These commands do not take time to optimize the Git data, since such optimizations scale with the full size of the repository while these user commands each perform a relatively small action.
git maintenance command provides flexibility for how to optimize the Git repository.
Run one or more maintenance tasks. If one or more
--task options are specified, then those tasks are run in that order. Otherwise, the tasks are determined by which
maintenance.<task>.enabled config options are true. By default, only
maintenance.gc.enabled is true.
commit-graph job updates the
commit-graph files incrementally, then verifies that the written data is correct. The incremental write is safe to run alongside concurrent Git processes since it will not expire
.graph files that were in the previous
commit-graph-chain file. They will be deleted by a later run based on the expiration delay.
Clean up unnecessary files and optimize the local repository. "GC" stands for "garbage collection," but this task performs many smaller tasks. This task can be expensive for large repositories, as it repacks all Git objects into a single pack-file. It can also be disruptive in some situations, as it deletes stale data. See git-gc for more details on garbage collection in Git.
When combined with the
run subcommand, run maintenance tasks only if certain thresholds are met. For example, the
gc task runs when the number of loose objects exceeds the number stored in the
gc.auto config setting, or when the number of pack-files exceeds the
gc.autoPackLimit config setting.
Do not report progress or other information over
If this option is specified one or more times, then only run the specified tasks in the specified order. If no
--task=<task> arguments are specified, then only the tasks with
maintenance.<task>.enabled configured as
true are considered. See the
TASKS section for the list of accepted
© 2012–2018 Scott Chacon and others
Licensed under the MIT License.