Optimize track_branches to avoid git checkout operation#773
Merged
Conversation
The track_branches operation is currently using a call to `git checkout` to set up the local branchs and track the proper remote. This means that we're actually updating the files on disk every time, which isn't necessary to establish the branch. Using a direct call to `git branch` is a LOT faster. Gemini 3 was used to help rewrite this function.
mjcarroll
approved these changes
May 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The track_branches operation is currently using a call to
git checkoutto set up the local branchs and track the proper remote. This means that we're actually updating the files on disk every time, which isn't necessary to establish the branch. Using a direct call togit branchis a LOT faster.Gemini 3 was used to help rewrite this function.
This appears to be roughly 10% faster when blooming large repositories even on a ramdisk. The savings would theoretically be far greater when running on an actual disk.