More progress details for clone, merge, fetch, push and pull
I was cloning my LFS repo today and it took a while, however the progress bar did not really help me see where it was and how long it had left. The GitHub client and others tells you what file it has left and how many files it has left and it would be grand to have this as well, especially if a clone gets stuck.
Under consideration Quality of Life Suggested by: Lindsay • Upvoted: 20 Feb • Comments: 11
Where is the progress bar?
More details on the progress of multiple long running operations would be usefull. Even Push/Pull Operations can sometimes take some time and it would be helpfull if the ongoing operation and more details about it would be more visible and prominent in the UI, instead of only showing a small rotating circle indicating some sort of operation going on
Seems since 8.0.0 there's this notification bar at the botom of the commit graph. That's nice. But still, if the LFS repo is a submodule and you're pulling the parent repo, you won't see anything and the repo could sit in there stuck for hours (in our case we have really large submodules containing game engine assets).
I find it problematic that the processes mentioned do not show how far they have progressed.
"General progress bar for clone, merge, fetch, push & pull" (suggested by Christoph on 2021-11-13), including upvotes (1) and comments (0), was merged into this suggestion.
When initializing a submodule, you click and you don't know if gitkraken is busy or not.
I suggest adding a busy indicator (loading bar, changing mouse cursor, animated icon etc)
Joey Kelroy Admin
"Add busy indicator for long running actions (i.e. init submodule)" (suggested by Oliver on 2022-09-26), including upvotes (1) and comments (0), was merged into this suggestion.
Can long running operations (cloning especially) not be blocking operations for the entire app. Please run that on a thread and let us interact with other repos in the meantime. I alternate between at least 4 repos daily, and if I can't do anything because I'm waiting for a long clone, that's just a waste of my time.
Frank Severinsen Merged
Fairly often we pull a repo and Gitkraken instantly confirms with "pulled succesfully" (which I know it isn't).
If I then wait ~30 secs and press pull again. it suddenly realise there are more changes needed to be pulled.
I don't know if fetching is not done automatically when pressing pull¸ or whats going, but it's very very problematic when we expect the repo to be pulled and up to date when Gitkraken says it is.
Chris Bowie Admin
"Stop saying "pulled succesfully" and "Already Up-to-Date" when it isn't" (suggested by Frank Severinsen on 2022-10-26), including upvotes (1) and comments (0), was merged into this suggestion.
+1 to needing better in-progress info and +1 to stopping the premature success messages