Add --force-progress option to opt-out the CI detection
#1261
Conversation
This file contains 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
theofidry
changed the title
maks-rafalko
approved these changes
Apr 25, 2020
|
We forgot about documenting this new option. Could you please add a PR to the docs? |
maks-rafalko
changed the title
--no-progress option to opt-out the CI detection
maks-rafalko
added a commit
to infection/site
that referenced
this pull request
Aug 3, 2020
Also, add a documentation for `--force-progress` option from infection/infection#1261
sanmai
changed the title
--no-progress option to opt-out the CI detection--force-progress option to opt-out the CI detection
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.
--force-progresswhich disables the CI detection, effectively ensuring the user will see all the progress bars and the mutation count (during the run – the ones in the summary are always displayed independently from noProgress)forceProgressandnoProgresscannot be set together both from the CLI or by manipulation the container directlyCiDetectorbyMemoizedCiDetectorwhich memoize the CI detection call