OU-1280: add claude backport command

[PeterYurkovich]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive backport workflow guide: dependency/version matrix for supported release branches, transformation references for framework/version mismatches, file-path complexity notes, common scenarios and troubleshooting, quick-reference commands, testing/lint checklist, and a PR checklist template for pushing backports.

[openshift-ci-robot]

@PeterYurkovich: This pull request references LOG-9015 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 bug to target the "5.0.0" version, but no target version was set.

Details

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

[PeterYurkovich]

/cherry-pick release-coo-ocp-4.22

[openshift-cherrypick-robot]

@PeterYurkovich: once the present PR merges, I will cherry-pick it on top of release-coo-ocp-4.22 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-coo-ocp-4.22

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.

[PeterYurkovich]

/label qe-approved
No QE needed

[coderabbitai]

Walkthrough

This PR adds a single comprehensive backport command guide (.claude/commands/backport.md) describing dependency-aware backport transformations (PatternFly, React Router), a step-by-step backport workflow, troubleshooting checklists, a PR template, and quick-reference commands.

Changes

Backport Command Documentation

Layer / File(s)	Summary
Adaptation guides and command metadata .claude/commands/backport.md	Front-matter and argument contract; dependency-version matrix; PatternFly v6 → v5 (and v4) transformation references and example snippets; React Router v7 → v6-compat → v5 guidance and mapping table.
Backport operational workflow .claude/commands/backport.md	Step-by-step procedure: analyze commit, compare web/package.json dependency versions, create backport branch, reinstall dependencies, cherry-pick or manually apply changes with conflict resolution, run lint/typecheck/unit tests and other verification commands, and push/create PR.
Troubleshooting and reference materials .claude/commands/backport.md	Common backport scenarios and troubleshooting checklist for dependency/module/type/test/build failures; backport PR template with adaptation checkboxes and testing expectations; quick-reference command block for commit/branch diffs, dependency checks, and interactive cherry-pick.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	This PR adds documentation (backport.md) and configuration files only. No test files or Ginkgo test code are modified, so the check for stable test names does not apply.
Test Structure And Quality	✅ Passed	The custom check is for Ginkgo test code quality, but this PR contains only a markdown documentation file and standard Go tests using testing.T, not Ginkgo tests. The check is not applicable.
Microshift Test Compatibility	✅ Passed	PR adds only a markdown documentation file (.claude/commands/backport.md) for backport workflows, not Ginkgo e2e tests. The check applies only to new e2e tests and is therefore not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No Ginkgo e2e tests are added in this PR. The single file added is a markdown documentation file (.claude/commands/backport.md) describing a backport workflow, not a Go test file.
Topology-Aware Scheduling Compatibility	✅ Passed	PR adds only a documentation file (.claude/commands/backport.md). No deployment manifests, operator code, or controllers are introduced, so topology-aware scheduling check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR adds only a markdown documentation file (.claude/commands/backport.md) with no executable code that could violate OTE binary stdout contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR adds only documentation (.claude/commands/backport.md) with no Ginkgo e2e tests; check is not applicable.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a claude backport command documentation file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

.claude/commands/backport.md (2)

99-100: 💤 Low value

Add blank line before table for markdown best practices.

Static analysis suggests adding a blank line before the table on line 100 to improve readability.

📝 Proposed fix

 Common v7/v6 → v5 changes:
+
 | v7/v6 (main/release-coo-ocp-4.22/release-coo-ocp-4.15)    | v5 (release-coo-ocp-4.12)  | Notes           |

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.claude/commands/backport.md around lines 99 - 100, Add a blank line before
the markdown table that begins with the header "Common v7/v6 → v5 changes:" so
there is an empty line between the preceding paragraph and the table row "|
v7/v6 (main/release-coo-ocp-4.22/release-coo-ocp-4.15)    | v5
(release-coo-ocp-4.12)  | Notes           |"; edit the block containing that
header and table row to insert one empty line immediately above the table.

---

54-55: 💤 Low value

Add blank line before table for markdown best practices.

Static analysis suggests adding a blank line before the table on line 55 to improve readability.

📝 Proposed fix

 Common v6 → v5 changes:
+
 | v6 (main) | v5 (release) | Notes |

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.claude/commands/backport.md around lines 54 - 55, Add a blank line
immediately before the markdown table that begins with the row "| v6 (main) | v5
(release) | Notes |" so the table is separated from the preceding paragraph;
edit the .claude/commands/backport.md content around that table header to insert
an empty line above it to satisfy Markdown best practices.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.claude/commands/backport.md:
- Line 124: Update the grep pattern used in the command that reads package.json
(the line starting with git show $1:web/package.json | grep -E ...) to match the
real package names: replace the incorrect tokens "patternfly.react-core" and
"dynamic-plugin-sdk": with the exact package names `@patternfly/react-core` and
`@openshift/dynamic-plugin-sdk`, and remove the stray trailing '":' typo; the
final regex should include `@patternfly/react-core`, react-router, and
`@openshift/dynamic-plugin-sdk` so the grep matches those package names correctly.
- Around line 211-213: Fix the typo "Obeservability" to "Observability" on the
three table rows and correct the PatternFly version assignments so they match
the Dependency Version Differences table: update the `release-coo-ocp-4.15` row
to use PatternFly v5 and `release-coo-ocp-4.12` to use PatternFly v4, keeping
`release-coo-ocp-4.22` as PatternFly v6; the three identifiers to edit are
`release-coo-ocp-4.22`, `release-coo-ocp-4.15`, and `release-coo-ocp-4.12`.

---

Nitpick comments:
In @.claude/commands/backport.md:
- Around line 99-100: Add a blank line before the markdown table that begins
with the header "Common v7/v6 → v5 changes:" so there is an empty line between
the preceding paragraph and the table row "| v7/v6
(main/release-coo-ocp-4.22/release-coo-ocp-4.15)    | v5 (release-coo-ocp-4.12) 
| Notes           |"; edit the block containing that header and table row to
insert one empty line immediately above the table.
- Around line 54-55: Add a blank line immediately before the markdown table that
begins with the row "| v6 (main) | v5 (release) | Notes |" so the table is
separated from the preceding paragraph; edit the .claude/commands/backport.md
content around that table header to insert an empty line above it to satisfy
Markdown best practices.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 1186474c-d2d7-41e0-8b40-8784828d75fb

📥 Commits

Reviewing files that changed from the base of the PR and between f4b8315 and d95e582.

📒 Files selected for processing (1)

• .claude/commands/backport.md

[openshift-ci-robot]

@PeterYurkovich: An error was encountered searching for bug LOG-9015 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message.

No response returned: Get "https://redhat.atlassian.net/rest/api/2/issue/LOG-9015": GET https://redhat.atlassian.net/rest/api/2/issue/LOG-9015 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

Summary by CodeRabbit

• Documentation
• Added a comprehensive backport workflow guide: dependency/version matrix for supported release branches, transformation references for framework/version mismatches, file-path complexity notes, common scenarios and troubleshooting, quick-reference commands, testing/lint checklist, and a PR checklist template for pushing backports.

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.

[zhuje]

/lgtm

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.claude/commands/backport.md:
- Around line 55-62: Add blank lines immediately before and after each Markdown
table block to satisfy MD058; locate the table beginning with the header row "|
v6 (main) | v5 (release) | Notes |" (and the similar table at the other
occurrence) and insert an empty line above the header and an empty line after
the final row so the table is separated from surrounding text. Ensure both the
table shown and the other occurrence (the block around lines 100-108) are
updated.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: a7c85fd3-8340-40a4-b03e-aa78a2fd6645

📥 Commits

Reviewing files that changed from the base of the PR and between d95e582 and 85d95f9.

📒 Files selected for processing (1)

• .claude/commands/backport.md

[openshift-ci-robot]

@PeterYurkovich: This pull request references OU-1280 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

• Documentation
• Added a comprehensive backport workflow guide: dependency/version matrix for supported release branches, transformation references for framework/version mismatches, file-path complexity notes, common scenarios and troubleshooting, quick-reference commands, testing/lint checklist, and a PR checklist template for pushing backports.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: PeterYurkovich, zhuje

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [PeterYurkovich,zhuje]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD f4b8315 and 2 for PR HEAD 85d95f9 in total

[PeterYurkovich]

/retest

[jgbernalp]

/test test-e2e

[openshift-ci]

@PeterYurkovich: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/test-e2e	85d95f9	link	true	/test test-e2e

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.