-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[4.x] Rename OpenStack -> common attributes across docs #22978
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
[4.x] Rename OpenStack -> common attributes across docs #22978
Conversation
The preview will be available shortly at: |
7e5ee5d
to
5c466e2
Compare
@openshift/team-documentation PTAL. Easy if tedious review. :) |
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! OCP 4.1 is no longer supported so unless you had a specific reason in mind, you shouldn't need to CP there.
@bobfuru Thanks! |
Just went on autopilot for 4.*. Won't bother CPing there. |
- Find and semi-manually sub in OSP attributes across most mods - RHOSP attribute sub in APIs module
5c466e2
to
6f90944
Compare
/cherry-pick enterprise-4.5 |
/cherry-pick enterprise-4.4 |
@maxwelldb: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","field":"head","code":"invalid"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"} In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick enterprise-4.3 |
@maxwelldb: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","field":"head","code":"invalid"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"} In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@maxwelldb: #22978 failed to apply on top of branch "enterprise-4.3":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick enterprise-4.4 |
@maxwelldb: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift/openshift-docs\n ! [rejected] cherry-pick-22978-to-enterprise-4.4 -> cherry-pick-22978-to-enterprise-4.4 (non-fast-forward)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift/openshift-docs'\nhint: Updates were rejected because the tip of your current branch is behind\nhint: its remote counterpart. Integrate the remote changes (e.g.\nhint: 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n", error: exit status 1 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick enterprise-4.5 |
Quite manual, it is. |
@maxwelldb: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift/openshift-docs\n ! [rejected] cherry-pick-22978-to-enterprise-4.5 -> cherry-pick-22978-to-enterprise-4.5 (non-fast-forward)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift/openshift-docs'\nhint: Updates were rejected because the tip of your current branch is behind\nhint: its remote counterpart. Integrate the remote changes (e.g.\nhint: 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n", error: exit status 1 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR resolves #22975.