Many discussions about Git focus on its basic functions, yet there’s less attention on optimizing Git for monorepos. With the release of Git v2.37.0, new features have been introduced that significantly improve performance for repositories with a lot of files. This blog post will cover custom git monorepo configurations to improve performance and providing step-by-step guidance on how to enhance your Git operations, especially in large-scale projects. We’ll look into these new features and explain how to effectively implement them in your global or local Git config.


Warning: Upgrade Git to 2.42.0+ and perform the steps in this tutorial on your main branch. `index.skipHash` causes errors on older Git versions.

Create a custom Git config file at ~/.gitconfig.monorepo

    commitgraph = true
    fsmonitor = true
    writeCommitGraph = true
    manyFiles = true

Include the custom configuration in your global or local Git config

    path = ~/.gitconfig.monorepo
    email =
    name = Darth Vader
    defaultBranch = main
    editor = nvim
    ui = auto
    autosetuprebase = always
    autoStash = true
    rebase = true
    default = current

Update Git index to version 4 in repo

Although feature.manyFiles sets the default index version, you need to manually update indexes on existing repositories in your terminal.

$ cd ~/example
$ git update-index --index-version 4

Start fsmonitor—daemon

$ cd ~/example
$ git fsmonitor--daemon start


By using the recommended approach listed above, my command execution time for “git status” was reduced from approximately 0.316 seconds to 0.118 seconds, accompanied by a decrease in CPU utilization from 425% to 89%, leading to a significantly improved performance. Additionally, I no longer encounter fatal: Unable to create 'project_path/.git/index.lock': File exists. errors while performing basic Git commands (MacOS Intel Core i9).


$ time git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
git status  0.21s user 1.14s system 425% cpu 0.316 total


$ time git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
git status  0.08s user 0.02s system 89% cpu 0.118 total

Explanation of configurations


Optimizes repositories with large numbers of files and commit histories. Enabling this configuration option enables the following by default:

Git writes an entirely new index in index.lock and then replaces .git/index when you use basic commands. In a monorepo with a large number of files, this index can be quite large and take several seconds to write every time you perform a command. Upgrading from the standard version 2 to version 4 reduces index size by 30%-50% by compressing the pathnames, which results in faster load time on operations. Caching untracked files adds more of a memory load but again, reduces the load time.

In my case, I encountered the following error often before I made the update:

fatal: Unable to create 'project_path/.git/index.lock': File exists.


Git will use a commit history cache to significantly speed up history operations, such as git log with the --graph option.


Improves performance of commands like git push -f and git log --graph by writing a commit-graph on every git fetch.

How to revert changes

In the event that experience an error or issues with your Git operations, revert the changes by doing the following:

  1. Update global or local Git config:
    1. Open your global or local Git config file.
    2. Remove or comment out the include path for the custom configuration:
    path = ~/.gitconfig.monorepo
  1. Revert index version in repo:
    1. Go to the specific repository (e.g., cd ~/example).
    2. If you want to revert the index version to a previous state (e.g., version 2), run the following command: git update-index --index-version 2
    3. Note: This step depends on your requirements and the original index version you were using.
  2. Stop fsmonitor daemon in repo:
    1. In the repository where you started the fsmonitor--daemon, stop it using git fsmonitor--daemon stop
    2. This will disable the file system monitor for that repository.
  3. General check and cleanup:
    1. Run git status to ensure that Git is working properly.