-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 28234: Make sure --record=false is acknowledged when passed to commands #10486
Conversation
[test] |
@damemi rebase needed (FAILURE: Generated docs up to date, but generated man pages out of date. Please run hack/update-generated-docs.sh) |
@smarterclayton when can we get generated docs etc out of the repo? Rebasing for an error like this shouldn't be necessary. |
It's probably pretty far down the priority list. |
5ee4a2d
to
1e22565
Compare
Evaluated for origin test up to 1e22565 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8254/) |
@ncdc were you ok with this one merging? Tests are green. |
LGTM [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8254/) (Image: devenv-rhel7_4907) |
Evaluated for origin merge up to 1e22565 |
Cherry-pick of upstream commit:
Ensures that when --record=false is explicity set that no ChangeCauseAnnotations are set on the object. Previously, if --record=true was used then all following actions triggered a ChangeCauseAnnotation even if --record=false was set, due to the prior ChangeCauseAnnotation existing.
Reference to bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1351127