-
Notifications
You must be signed in to change notification settings - Fork 28.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git: Provide task progress #62751
Comments
My two cents:
So while it is possible to provide a certain degree of the operation progress, there are different unknown parts which are effectively untraceable. That percentages are only a part of the push process. |
As basic implementation It could be enough to handle the git 'stdinfo' outoput and show it inside the git output console (maybe optionally with some "show git verbose output" flag in the settings). |
+1 |
I am not sure if I think a progress can been done correctly as the remote may be doing much more then normal git commands, but I do think there should be some sort of way to see the raw output from the remote which there doesn't seem to be unless your run all your git commands from the Terminal which I would prefer not to. I created a separate issue for that: #85732 |
The issue description did not mention hook progress explicitly, but git hooks can take more time than the actual git operation, and the hook progress is not visible. GUIs like GitExtensions would show a dialog with the progress of the entire operation, including the hooks. |
Request
It could be a nice feature to show the git progress details in the GIT output console or since Visual Studio even though is 'Code' has the characteristic to being 'Visual', polish the user interface with some indicator.
In the following images there are some suggestions:
Use case
It happen sometime that users have in their own repository some big amount files or maybe the connection slow down during the 'git push', users don't have any idea what is happening or what is the current operation state (it could take even plenty of minutes).
In the example I'have done, this is what is showed actually in VS Code:
And this is what it can be read from the git executable output:
Advantages
Users that have this kind of experience can think that the git integration (that is already amazing in VS Code) is not working very good because the operations appears 'blocked'. So they give up and jump on the CLI for the daily usage of git. With some nice improvements like I showed they wouldn't do it.
Technical inspection
I inspected the main source code file about the default GIT extension:
https://github.com/Microsoft/vscode/blob/master/extensions/git/src/git.ts
A nice implementation could be extract more information on the 'git commands output' parsing, ex. Operation 'N' of 'M' and 'Percentage', expose it and use on higher layer of Visual Studio Code.
Waiting for a your feedback.
Thank you.
The text was updated successfully, but these errors were encountered: