Skip to content

OSDOCS-19543: Add 4.22 release note for GuidedTourFeature console capability#111243

Open
jseseCCS wants to merge 1 commit intoopenshift:enterprise-4.22from
jseseCCS:OSDOCS-19543-NEW
Open

OSDOCS-19543: Add 4.22 release note for GuidedTourFeature console capability#111243
jseseCCS wants to merge 1 commit intoopenshift:enterprise-4.22from
jseseCCS:OSDOCS-19543-NEW

Conversation

@jseseCCS
Copy link
Copy Markdown
Contributor

@jseseCCS jseseCCS commented May 5, 2026

…ability

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19543

Link to docs preview:

QE review: N/A for RNs

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 5, 2026

@jseseCCS: This pull request references OSDOCS-19543 which is a valid jira issue.

Details

In response to this:

…ability

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19543

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 5, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 5, 2026

Hi @jseseCCS. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@jseseCCS
Copy link
Copy Markdown
Contributor Author

jseseCCS commented May 5, 2026

in review with @logonoff

@jseseCCS jseseCCS force-pushed the OSDOCS-19543-NEW branch from 031f38d to f341a10 Compare May 5, 2026 15:35
@jseseCCS
Copy link
Copy Markdown
Contributor Author

jseseCCS commented May 5, 2026

image

LGTM from Jackson

@jseseCCS
Copy link
Copy Markdown
Contributor Author

jseseCCS commented May 5, 2026

/label merge-review-needed

@openshift-ci openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label May 5, 2026
Copy link
Copy Markdown
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 5, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

🤖 Tue May 05 16:19:52 - Prow CI generated the docs preview:

https://111243--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-22-release-notes.html

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 5, 2026

@jseseCCS: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. merge-review-needed Signifies that the merge review team needs to review this PR needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants