Skip to content

Conversation

@abrennan89
Copy link
Contributor

@abrennan89 abrennan89 commented Dec 23, 2025

Version(s):
Will CP back as far as possible without conflicts; at least 4.20+

Issue:
https://issues.redhat.com/browse/DOCPLAN-31

Link to docs preview:

QE review:
N/A

Additional information:
Per the CQA, it wasn't clear whether this section should be a procedure or a reference module. It was formatted as reference, but didn't really seem to fit that template. However, it also didn't make sense as a procedure module or even a .Troubleshooting section, since there isn't really a set of steps provided. I've opted to move this into a step in the main procedure meet migration requirements. The structure can be revisited during the JTBD work and CNV overall restructure later if required.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 23, 2025

@abrennan89: This pull request references DOCPLAN-31 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):
Will CP back as far as possible without conflicts; at least 4.20+

Issue:
https://issues.redhat.com/browse/DOCPLAN-31

Link to docs preview:

QE review:
N/A

Additional information:
Per the CQA, it wasn't clear whether this section should be a procedure or a reference module. It was formatted as reference, but didn't really seem to fit that template. However, it also didn't make sense as a procedure module or even a .Troubleshooting section, since there isn't really a set of steps provided. I've opted to move this into an admonition for now to meet migration requirements. The structure can be revisited during the JTBD work and CNV overall restructure later if required.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 23, 2025
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 23, 2025
@abrennan89 abrennan89 changed the title DOCPLAN-31: Remove unnecessary module, move to admonition [WIP] DOCPLAN-31: Remove unnecessary module, move to admonition Dec 23, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 23, 2025

@abrennan89: This pull request references DOCPLAN-31 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):
Will CP back as far as possible without conflicts; at least 4.20+

Issue:
https://issues.redhat.com/browse/DOCPLAN-31

Link to docs preview:

QE review:
N/A

Additional information:
Per the CQA, it wasn't clear whether this section should be a procedure or a reference module. It was formatted as reference, but didn't really seem to fit that template. However, it also didn't make sense as a procedure module or even a .Troubleshooting section, since there isn't really a set of steps provided. I've opted to move this into a step in the main procedure meet migration requirements. The structure can be revisited during the JTBD work and CNV overall restructure later if required.

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
Copy link

openshift-ci bot commented Dec 23, 2025

@abrennan89: 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

branch/enterprise-4.20 branch/enterprise-4.21 CNV Label for all CNV PRs do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants