Update repo-brancher-controller forwarding for 5.1

[deepsm007]

/cc @openshift/test-platform

/hold

Summary by CodeRabbit

• Updates repo-brancher-controller promotion configuration for the 5.1 release.
• Changes the release branch source from 5.0 to 5.1 and advances the promotion target from 5.1 to 5.2.
• Affects OpenShift CI infrastructure for repository branch forwarding.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: b93d1716-275e-4234-b794-be1826040dd8

📥 Commits

Reviewing files that changed from the base of the PR and between 9a1ce57 and 9cec838.

📒 Files selected for processing (1)

• clusters/app.ci/repo-brancher-controller/repo-brancher-controller.yaml

---

Walkthrough

The repo-brancher-controller configuration now promotes from release branch 5.1 to targets 5.1 and 5.2. OpenShift promotion targets use the same versions.

Changes

Repo brancher promotion

Layer / File(s)	Summary
Promotion configuration clusters/app.ci/repo-brancher-controller/repo-brancher-controller.yaml	The default and OpenShift promotion targets changed from 5.0/5.1 to 5.1/5.2. The release branch source changed from 5.0 to 5.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 9cec8

This is a localized forwarding configuration update with no supplied concrete correctness or merge-readiness issue; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: jmguzik

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the repo-brancher-controller forwarding update for version 5.1.
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	The pull request changes only static forwarding values in a ConfigMap; it adds no Ginkgo test titles or dynamic test-name content.
Test Structure And Quality	✅ Passed	The diff changes only a YAML ConfigMap; it adds no Ginkgo test code, cluster waits, setup/cleanup, or assertions to review.
Microshift Test Compatibility	✅ Passed	The diff changes only repo-brancher-controller YAML promotion values. It adds no Ginkgo e2e tests or test references to MicroShift-unsupported APIs or features.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only repo-brancher-controller YAML forwarding values; it adds no Ginkgo e2e tests or multi-node test behavior.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff changes only repo-brancher forwarding versions and release source; it adds no topology, affinity, replica, selector, toleration, spread, or PDB scheduling constraint.
Ote Binary Stdout Contract	✅ Passed	The parent-to-HEAD diff changes only four forwarding values in a ConfigMap YAML; it adds no process-level code or stdout writes covered by this check.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only repo-brancher-controller YAML forwarding values; it adds no Ginkgo e2e tests or new IPv4 assumptions or external connectivity requirements.
No-Weak-Crypto	✅ Passed	The parent-to-HEAD diff only changes branch forwarding values in one YAML ConfigMap; no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, or crypto implementation appears.
Container-Privileges	✅ Passed	The diff changes only repo-brancher forwarding values. It introduces no privileged, host namespace, SYS_ADMIN, allowPrivilegeEscalation, or root-related setting.
No-Sensitive-Data-In-Logs	✅ Passed	The parent diff changes only branch-forwarding values (5.0/5.1/5.2); it adds no logging code or sensitive data to log output.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@deepsm007: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

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

[danilo-gemoli]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danilo-gemoli, deepsm007

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:

• clusters/OWNERS [danilo-gemoli,deepsm007]

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