-
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
use quiet #18
Comments
We can provide an option to turn on
|
Didn't know the command option was available. |
@FernandoMiguel we don't have it right now, we can consider adding it. 😄 |
The docs or the flag? 🤔 |
the flag. 😄 |
Damn it... |
This is what I get for half reading comments while having breakfast. |
Agree with OP, the log seems to be quite verbose:
But I can also see it being useful. I wish there was a way to disable that though. I am not really watching checkout ever. |
Problem is, Actions tab really have problems with handling long and quickly updating steps, up to the point that it's freezing browser while action is running. That's UI issue, not anything wrong with action itself, but TL;DR i'd like having |
Marking as enhancement and I'll defer to others. Personally, +1 what @TingluoHuang said. Sense of motion and timestamps are good for us to help customers. I'm generally hesitant to add extra inputs (overload user with options). |
I feel like the real solution here would be to add support for the carriage return clearing the line. |
Output from the step is now grouped so that should help. |
group doesn't help much if you're reading raw logs... can we please have |
@ericsciple plz reopen, it's still wasteful/unhelpful to have all these extra log lines |
For big project like https://github.com/trinodb/trino where we have plenty of jobs (currently 35) we we run very often (like 40 times per day). We are pretty sure that is working just fine as it has never failed for us (at least I don't recall a case), but still every single log file has about 170 lines with git progress that does not add any value. We usually read the raw log file as UI is not responsive with such huge log files (browser is not much responsive too but it is a bit better with raw files). Maybe we could have |
The amount of logs this generates is insane. Please consider at least giving us the option to quiet it down. |
Just to add another POV: depending on how many jobs/runs and the nature of them, a repo can quickly use large amounts of storage space to accommodate these logs. I fail to see how the proposed flag could be a problem. |
Please reopen |
FYI I think I have a good solution for this, see #1067 . |
currently the checkout performs:
git -c http.extraheader="AUTHORIZATION: basic ***" fetch --tags --prune --progress --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/*
would be great to use quiet instead
git -c http.extraheader="AUTHORIZATION: basic ***" fetch --tags --prune --quiet --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/*
so the job log is cleaner to read
The text was updated successfully, but these errors were encountered: