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
push: --force-compression
should be true
with --compression-format
#5013
Conversation
With discussion from here: containers/podman#19640, it was decided that `--force-compression` must be automatically `true` in case when `--compression-format` is set. Signed-off-by: Aditya R <arajan@redhat.com>
@containers/buildah-maintainers @vrothberg @giuseppe @mtrmac PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, giuseppe, vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
if c.Flag("compression-format").Changed { | ||
if !c.Flag("force-compression").Changed { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This can be if a && !b { }
, saving one level of nesting.)
With discussion from here:
containers/podman#19640, it was decided that
--force-compression
must be automaticallytrue
in case when--compression-format
is set. Following PR does that and makes behavior ofpodman
andbuildah
consistent.What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?