Feature: fast staging for large repositories #1856
Open
+70
−9
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.
I am currently working exclusively with a large codebase. The main issue is that
git statuson the entire repo takes around 2 seconds which makes staging and committing super tedious and frustrating.Here's a hacky implementation that runs
git statusonly on touched files during staging. There is also an autocommand that keeps the status buffer up-to date in the background.There is a slight drawback for renamed files with the current implementation, so I added a configuration option.