Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.22from
bryan-cox:add-gha-422-release
Apr 13, 2026
Merged

CNTRLPLANE-3233: ci(gha): add release-4.22 branch to GitHub Actions workflows#8218
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.22from
bryan-cox:add-gha-422-release

Conversation

@bryan-cox
Copy link
Copy Markdown
Member

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 lint job correctly fetches the base branch ref

🤖 Generated with Claude Code

Add the release-4.22 branch to all applicable GHA workflow triggers so
PRs and pushes to that branch receive the same CI coverage as main.

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

The lint workflow's hardcoded `git fetch origin main:main` is replaced
with a dynamic `github.base_ref` reference so it works correctly for
PRs targeting any configured branch.

sync-community-fork is excluded as it is only relevant for main.

Resolves: CNTRLPLANE-3233

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 13, 2026

@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 lint job correctly fetches the base branch ref

🤖 Generated with Claude Code

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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 13, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 13aca5c2-3cdf-4de6-afa7-2a6533831129

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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 openshift-ci bot requested review from enxebre and sjenning April 13, 2026 13:15
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 13, 2026

[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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 13, 2026
@bryan-cox
Copy link
Copy Markdown
Member Author

/area ci-tooling

@openshift-ci openshift-ci bot added area/ci-tooling Indicates the PR includes changes for CI or tooling and removed do-not-merge/needs-area labels Apr 13, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 13, 2026

@bryan-cox: 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.

@bryan-cox
Copy link
Copy Markdown
Member Author

/verified by gha

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@bryan-cox: This PR has been marked as verified by gha.

Details

In response to this:

/verified by gha

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.

@sjenning sjenning added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 13, 2026
@sjenning
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 13, 2026
@sjenning sjenning added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 13, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 3ca0307 into openshift:release-4.22 Apr 13, 2026
10 checks passed
@bryan-cox bryan-cox deleted the add-gha-422-release branch April 13, 2026 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ci-tooling Indicates the PR includes changes for CI or tooling backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants