Discard all changes is very slow, far slower than git checkout -- .
See original GitHub issueDescription
Discard changes is very slow, far slower than git checkout – . For instance, for >800 files changes to discard, it last several minutes
Version
GitHub Desktop version: 0.8.0
OS version: Microsoft Windows [version 10.0.15063]
Steps to Reproduce
- Make >500 changes
- Select all, and clic right “Discard changes”
- Compare with same changes and
git checkout -- .
in bash
Expected behavior: faster, close to bash command time
Actual behavior: very slow
Reproduces how often: 100%
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Git Status Takes a Long Time to Complete - Stack Overflow
If it's still slow, then it sounds like a system or hardware issue. Git finishes status on hundreds of files for me in...
Read more >Git is extremely slow on Windows - Super User
Various commands working with local files are slow, e.g. status & commit . push is fast. Windows 10, Git 2.11.0 64 bit, high...
Read more >How to discard your local changes in Git example
Git reset doesn't discard all local changes. The git reset –hard command will revert uncommitted changes that exist in files that have been ......
Read more >Improve Git monorepo performance with a file system monitor
These commands are slow because they need to search the entire worktree looking for changes. When the worktree is very large, Git needs...
Read more >git really slow on Windows - Google Groups
Windows is just plain slower than Linux at operating on many small files. > We see this behaviour across all of our repositories;...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m encountering this when switching from a branch that ignores node_modules to one that does not. I might have 10,000 files to discard. I’ve learnt it’s best to just go and shift+delete the folder rather than attack it through github desktop.
This needs an option to discard the files without recovery, and some text that warns of the cost. It’s ludicrous how long this takes