You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all! Loving GitButler, really excited for when all the quirks are ironed out, very happy to help with that!
I wondered if you could add some warning, or loading loop after X seconds, if the app is crunching through a lot of background tasks?
I ran cargo vendor for the first time and it was a minute before I realised why GitButler was unresponsive and everything was erroring. The command downloads all your dependencies' source code into your repository. I eventually added it to my .gitignore but I was holding my breath for a little while there. (It was around 30,000 new files, my MacBook Pro M3 spun to 100% CPU).
Just an idea
The text was updated successfully, but these errors were encountered:
I am 100% sure this will be fixed with the major release. 30k new files will still take a moment to obtain a status for, but the application won't automatically diff everything anymore, which should reduce the overhead significantly.
Using cargo vendor is something I think we will try with what's code-named as v3 as well to see how it fares.
Hi all! Loving GitButler, really excited for when all the quirks are ironed out, very happy to help with that!
I wondered if you could add some warning, or loading loop after X seconds, if the app is crunching through a lot of background tasks?
I ran
cargo vendor
for the first time and it was a minute before I realised why GitButler was unresponsive and everything was erroring. The command downloads all your dependencies' source code into your repository. I eventually added it to my .gitignore but I was holding my breath for a little while there. (It was around 30,000 new files, my MacBook Pro M3 spun to 100% CPU).Just an idea
The text was updated successfully, but these errors were encountered: