We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the pre- and post-receive calls introduced in #8602, Gitea now sends messages to the pushing client, for example:
remote: * Checking 1 branches remote: Checked 1 references in total remote: . Processing 1 references remote: Processed 1 references in total
Since git always displays this messages, even when called with --quiet, it would be great if these messages could be turned off.
--quiet
The text was updated successfully, but these errors were encountered:
So perhaps some explanation is in order.
This was added to prevent pre-receive and post-receive timing out when multiple branches & tags are pushed. By multiple I mean > 100.
Hmm...
Maybe we could stack these up and only display them if you push more than 30 references?
Sorry, something went wrong.
What about a timer? Many programs show up the progress report only after it's taking longer than a certain time.
If --quiet can be detected on the server side we could print \r instead (which is mostly invisible... except on Mac, of course).
\r
I've put a simple PR up that won't print anything if the hook runs for less than one second.
This may need a longer delay or a setting.
Successfully merging a pull request may close this issue.
With the pre- and post-receive calls introduced in #8602, Gitea now sends messages to the pushing client, for example:
Since git always displays this messages, even when called with
--quiet
, it would be great if these messages could be turned off.The text was updated successfully, but these errors were encountered: