feat: add --no-progress and auto-skip bars when piped - #391
Merged
Conversation
Problem: The spinner consumes nix's output, so piping a deploy into nix-output-monitor or CI logs showed nothing useful. Solution: Only show the spinner on a terminal, and add --no-progress to force it off; otherwise nix's output (or --log-format internal-json) is forwarded directly.
Sereja313
force-pushed
the
sereja/no-progress-flag
branch
from
August 5, 2026 01:02
f6ca91b to
ebe7e47
Compare
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
1 participant
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.
Problem: The spinner consumes nix's output, so piping a deploy into nix-output-monitor or CI logs showed nothing useful.
Solution: Only show the spinner on a terminal, and add --no-progress to force it off; otherwise nix's output (or --log-format internal-json) is forwarded directly.
Fixes #386