Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use --progress to configure progress UI style #10690

Merged
merged 1 commit into from
Jun 12, 2023
Merged

Conversation

ndeloof
Copy link
Contributor

@ndeloof ndeloof commented Jun 12, 2023

What I did
Introduce --progress top-level flag to configure progress UI as auto|tty|plain|quiet|none

This allows to have explicit control on the progress UI without using --ansi flag which also has impact on logs rendering

build already declared this flag. It is now redundant and kept for backward compatibility but marked hidden

Related issue
see #10686

(not mandatory) A picture of a cute animal, if possible in relation to what you did

@ndeloof ndeloof requested review from a team, nicksieger, StefanScherer, ulyssessouza, glours, milas and laurazard and removed request for a team June 12, 2023 07:38
@ndeloof ndeloof force-pushed the progress branch 2 times, most recently from 8a7ac24 to 1f20407 Compare June 12, 2023 07:49
Copy link
Contributor

@milas milas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Hurray for CLI consistency

(I mean I'm not thrilled that progress.Mode is a global but that's not new 😛)

@ndeloof ndeloof force-pushed the progress branch 2 times, most recently from a32915f to 000d3a3 Compare June 12, 2023 13:33
@ndeloof
Copy link
Contributor Author

ndeloof commented Jun 12, 2023

@milas made a last minute update : to avoid --progress for being documented on each and every command, I made build --progress a simple duplicate to set the same variable, and marked flag hidden so we keep backward compatibility but docs are relevant for recommended usage.

@codecov
Copy link

codecov bot commented Jun 12, 2023

Codecov Report

Patch coverage: 36.84% and project coverage change: -0.14 ⚠️

Comparison is base (68bd0eb) 58.98% compared to head (000d3a3) 58.85%.

❗ Current head 000d3a3 differs from pull request most recent head 43665d4. Consider uploading reports for the commit 43665d4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##               v2   #10690      +/-   ##
==========================================
- Coverage   58.98%   58.85%   -0.14%     
==========================================
  Files         111      112       +1     
  Lines        9716     9740      +24     
==========================================
+ Hits         5731     5732       +1     
- Misses       3399     3419      +20     
- Partials      586      589       +3     
Impacted Files Coverage Δ
pkg/progress/quiet.go 0.00% <0.00%> (ø)
pkg/progress/writer.go 61.53% <0.00%> (-2.47%) ⬇️
cmd/compose/compose.go 70.94% <41.66%> (-2.02%) ⬇️
cmd/compose/build.go 81.15% <80.00%> (+6.83%) ⬆️

... and 4 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Contributor

@glours glours left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ndeloof ndeloof enabled auto-merge (rebase) June 12, 2023 14:34
@ndeloof ndeloof merged commit cfe91be into docker:v2 Jun 12, 2023
@ndeloof ndeloof deleted the progress branch June 13, 2023 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants