Skip to content

OSDOCS#17076: Updates CQA pt 2#106919

Open
skopacz1 wants to merge 1 commit intoopenshift:mainfrom
skopacz1:OSDOCS-17076_2
Open

OSDOCS#17076: Updates CQA pt 2#106919
skopacz1 wants to merge 1 commit intoopenshift:mainfrom
skopacz1:OSDOCS-17076_2

Conversation

@skopacz1
Copy link
Contributor

@skopacz1 skopacz1 commented Feb 18, 2026

OSDOCS-17076

Version(s): 4.16+

Note to reviewer: with the exception of some short descriptions, this has almost no new content. All the big blocks in the diff are me moving content into new modules.

This PR is the second of two PRs to CQA the understanding updates section.

QE review: Just CQA changes, if anything appears to change technical accuracy feel free to let me know

Previews:
Understanding update channels and releases
Understanding OpenShift update duration

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

openshift-ci-robot commented Feb 18, 2026

@skopacz1: This pull request references OSDOCS-17076 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):

Issue:

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 the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 18, 2026
Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] RedHat.TermsErrors: Use 'for example' rather than 'For instance'. For more information, see RedHat.TermsErrors.

Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] RedHat.TermsErrors: Use 'several' rather than 'a number of'. For more information, see RedHat.TermsErrors.

Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] AsciiDocDITA.DocumentTitle: The document title (a level 0 heading) is missing.

@skopacz1 skopacz1 force-pushed the OSDOCS-17076_2 branch 2 times, most recently from 729a389 to 224953c Compare February 18, 2026 19:41
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2026

@skopacz1: This pull request references OSDOCS-17076 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

OSDOCS-17076

Version(s): 4.16+

This PR is the second of two PRs to CQA the understanding updates section.

QE review: Just CQA changes, if anything appears to change technical accuracy feel free to let me know

Previews:
Understanding update channels and releases
Understanding OpenShift update duration

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.

@skopacz1 skopacz1 changed the title OSDOCS-17076: Updates CQA pt 2 OSDOCS#17076: Updates CQA pt 2 Feb 18, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 18, 2026
@openshift-ci-robot
Copy link

@skopacz1: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

OSDOCS-17076

Version(s): 4.16+

This PR is the second of two PRs to CQA the understanding updates section.

QE review: Just CQA changes, if anything appears to change technical accuracy feel free to let me know

Previews:
Understanding update channels and releases
Understanding OpenShift update duration

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.

Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] AsciiDocDITA.DocumentTitle: The document title (a level 0 heading) is missing.

@skopacz1
Copy link
Contributor Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Feb 18, 2026

@skopacz1: 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.

@skopacz1 skopacz1 added the merge-review-needed Signifies that the merge review team needs to review this PR label Feb 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-needed Signifies that the merge review team needs to review this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments