Suppress verbose git checkout --detached output with --quiet#2379
Open
maschwenk wants to merge 4 commits intoactions:mainfrom
Open
Suppress verbose git checkout --detached output with --quiet#2379maschwenk wants to merge 4 commits intoactions:mainfrom
git checkout --detached output with --quiet#2379maschwenk wants to merge 4 commits intoactions:mainfrom
Conversation
Replace --progress with --quiet in checkout() and add --quiet to checkoutDetach() to prevent per-file output from flooding CI logs on large repositories. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Make checkout() and checkoutDetach() accept showProgress so callers can opt into --progress output; default remains --quiet - Pass settings.showProgress to checkout() from git-source-provider - Fix fetchOptions.showProgress not being set (was always undefined) - Rebuild dist Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maschwenk
changed the title
git checkout --detached output with --quiet
|
good stuff, +1 for merging this 👍🏻 |
maschwenk
commented
Feb 26, 2026
Comment on lines
80
to
+81
| show-progress: | ||
| description: 'Whether to show progress status output when fetching.' | ||
| description: 'Whether to show progress status output for git operations.' |
Author
There was a problem hiding this comment.
show-progress does not really imply this is exclusively related to fetch. Only this little helptext.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When
actions/checkoutruns against a large repository,git checkout --detachoutputs every file being written to the log.For repos with thousands of files this floods the GitHub Actions log. For our repo this was something like 80k log lines. Why does this matter? Because when Agents read Github Actions logs (which are already chatty) they can easily consume 80k lines of noise for no reason. There are methods for avoiding that, but this output also seems low-value as-is.
In this PR:
I initially was just going to target
checkoutDetachbut then realized there was an existingprogressconfig. I figured maybe a more holistic approach would be to reuse this concept. So I have:--progresswith--quietincheckout()to suppress per-file output during checkout--quiettocheckoutDetach()for the same reasonshowProgressthroughcheckout()andcheckoutDetach()so callers can still opt into--progressoutput; default remains--quietfetchOptions.showProgressnot being set ingit-source-provider.ts(was alwaysundefined, so--progresswas never applied to fetch either)show-progressdescription from fetch-specific to all git operationsUsers can set
show-progress: true(the default) to keep verbose output, orshow-progress: falseto quiet all git operations.Alternatively, can keep this very directly constrained to the detached checkout
(note to self, do not rebase this branch as we are referencing it a specific commit in it already)