feat(cli): disable progress bar in CI environment #1040
Merged
Conversation
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
github-actions
bot
added
📖 Project documentation
matejchalk
force-pushed
the
progress-off-in-ci
branch
from
e1745ab to
1244681
Compare
vmasek
approved these changes
Jul 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The immediate motivation for this change is to avoid
--no-progressargument being used in CI, which is part of an effort to avoid extra CLI arguments which restrict cache reuse in Nx monorepos.In the future, we'd like to get rid of the progress bar completely and replace it with a spinner. Either way, it would make sense to only show these UI elements when not in running in CI. The
--progressargument may be removed in the future though, we'll see. The future improvements are part of a larger effort, see:I've created some general purpose utility functions for correctly parsing boolean environment variables, so it now supports conventions like
true/false,1/0,yes/no,on/off, etc. I've reused those for theCP_VERBOSEvariable as well.