CNTRLPLANE-3233: ci(gha): add release-4.22 branch to GitHub Actions workflows

[bryan-cox]

Summary

• Add release-4.22 to the branch triggers for all applicable GitHub Actions workflows so PRs targeting that branch get the same CI checks as main
• Replace hardcoded git fetch origin main:main in lint workflow with dynamic github.base_ref reference
• sync-community-fork.yaml excluded (only relevant for main)

Updated workflows: codespell, cpo-container-sync, docs-preview, envtest-kube, envtest-ocp, gitlint, lint, test, verify

Resolves: CNTRLPLANE-3233

Test plan

• Verify GHA workflows trigger on PRs targeting release-4.22
• Verify GHA workflows still trigger on PRs targeting main
• Verify lint job correctly fetches the base branch ref

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow configurations to enable automated testing, verification, linting, and documentation processes on the release-4.22 branch in addition to the main development branch.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

📝 Walkthrough

Walkthrough

Multiple GitHub Actions workflows were updated to expand their trigger conditions. Each workflow now includes the release-4.22 branch alongside main in their branches filter for push, pull_request, or pull_request_target events. The affected workflows are: codespell, cpo-container-sync, docs-preview, envtest-kube, envtest-ocp, gitlint, lint, test, and verify. Additionally, the lint workflow was updated to dynamically use the PR base branch reference instead of a hardcoded main branch in its git fetch command.

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 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.
Stable And Deterministic Test Names	✅ Passed	PR modifies only GitHub Actions workflow files without changing any Ginkgo test code, making the stable test names check not applicable.
Test Structure And Quality	✅ Passed	This custom check reviews Ginkgo test code quality, but the PR contains only GitHub Actions workflow configuration changes with no test code files modified.
Microshift Test Compatibility	✅ Passed	PR only modifies GitHub Actions workflow files in .github/workflows/ directory. No new Ginkgo e2e test code (It(), Describe(), Context(), When(), etc.) has been added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only GitHub Actions workflow YAML files without adding new Ginkgo e2e tests, making SNO Test Compatibility check not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only GitHub Actions workflow files to extend CI/CD triggers to release-4.22 branch; contains no deployment manifests, operator code, or Kubernetes scheduling configurations.
Ote Binary Stdout Contract	✅ Passed	PR only modifies GitHub Actions workflow YAML configuration files, not executable application code. OTE Binary Stdout Contract check targets process-level code entry points.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Go test files in diff; PR only modifies GitHub Actions workflow YAML files for release-4.22 branch CI triggers.
Title check	✅ Passed	The title accurately and specifically describes the main change: adding release-4.22 branch support to GitHub Actions workflows.

_{✏️ 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.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox

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 [bryan-cox]

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

[openshift-ci-robot]

@bryan-cox: This pull request references CNTRLPLANE-3233 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Add release-4.22 to the branch triggers for all applicable GitHub Actions workflows so PRs targeting that branch get the same CI checks as main
• Replace hardcoded git fetch origin main:main in lint workflow with dynamic github.base_ref reference
• sync-community-fork.yaml excluded (only relevant for main)

Updated workflows: codespell, cpo-container-sync, docs-preview, envtest-kube, envtest-ocp, gitlint, lint, test, verify

Resolves: CNTRLPLANE-3233

Test plan

• Verify GHA workflows trigger on PRs targeting release-4.22
• Verify GHA workflows still trigger on PRs targeting main
• Verify lint job correctly fetches the base branch ref

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
• Updated CI/CD workflow configurations to enable automated testing, verification, linting, and documentation processes on the release-4.22 branch in addition to the main development branch.

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.

[bryan-cox]

/area ci-tooling

[jparrill]

/lgtm

[openshift-merge-bot]

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

• The changed files don't match any pipeline_run_if_changed patterns
• All files match pipeline_skip_if_only_changed patterns
• No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

[jparrill]

/verified by Github Actions

[openshift-ci-robot]

@jparrill: This PR has been marked as verified by Github Actions.

Details

In response to this:

/verified by Github Actions

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.

[dgoodwin]

This popped up as a pr without coderabbit review, any idea why? Was this opened in draft by any chance?