-
Notifications
You must be signed in to change notification settings - Fork 1.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
Run git fetch with --quiet
by default
#489
Comments
Found #18... |
I find this jarring to the viewer (the text scrolls faster than it can be read). It is also a waste of bandwidth. It's not that much bandwidth individually, but at scale the waste must be impressive. Has a way been implemented/documented for disabling this noisy output? |
@oowekyala I don't think this should be closed because #18 was closed as "resolved" due to them adding log grouping/collapsing to the UI. But the fact is, it doesn't solve the huge amount of logs this needlessly generates. So I think there should be some open issue about this so it's addressed. |
@Allon-Guralnek I think you're right, but I think it would be more appropriate for the original ticket to be reopened |
FYI there's a PR for this at #1067. |
The log output would be cleaner if the clone/fetch command used the
--quiet
option. This way, the download progress would not be output in logs:Currently this prints one line per 1 or 2 % progress, for each of
remote: Counting objects
,remote: Compressing objects
,Receiving objects
, andResolving deltas
. This is as much as 400 lines of useless logs, maybe more for very big repos.The text was updated successfully, but these errors were encountered: