git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git push --quiet is not quiet

From
Hanno Böck <hanno@hboeck.de>
Date
May 19, 2023, 09:09 UTC
Message-ID
<20230519110937.7df62fd7.hanno@hboeck.de>
In-Reply-To
<20230519090559.GA3515410@coredump.intra.peff.net>

On Fri, 19 May 2023 05:05:59 -0400 Jeff King <peff@peff.net> wrote:

> As a guess, I wondered if you might be pushing to GitHub.
Yes.
Show 5 quoted lines
> So I think this is a bug / lack of feature in GitHub's server
> implementation.  It used to be a thin proxy around Git (and Git has
> supported "quiet" since c207e34f7733 in 2012). But I suspect they may
> have recently replaced it with something more custom (based on the
> agent field).

Ok, interesting. Maybe add to this: it appears github sometimes uses this channel to send relevant messages, e.g. dependabot alerts. Which I guess is a good thing, but it probably shouldn't send status messages for normal commits when the user asks for "quiet".

-- 
Hanno Böck
https://hboeck.de/
Previous: Jeff KingNext: Jeff King
Message 4 of 7 in “git push --quiet is not quiet”
  1. Hanno BöckMay 19, 2023
  2. Kristoffer HaugsbakkMay 19, 2023
  3. Jeff KingMay 19, 2023
  4. Hanno BöckMay 19, 2023
  5. Jeff KingMay 19, 2023
  6. Taylor BlauJun 5, 2023
  7. Jeff KingJun 6, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.