1.5: Skip upstream-only workflows on this fork (cherry-pick velero-io/velero#10001)

[kaovilai]

Cherry-pick of velero-io#10001.

Guards several upstream-only GitHub Actions workflows (auto_assign_prs, auto_label_prs, auto_request_review, pr-changelog-check, prow-action, rebase, stale-issues, pr-codespell) with if: github.repository == 'velero-io/velero', so they skip on this fork instead of running here and failing due to missing secrets/config or duplicating this repo's own automation.

pr-filepath-check.yml doesn't exist on this branch, so that guard was dropped (nothing to guard).

Also includes CI-health fixes matching the same class already applied upstream (release-1.14 through release-1.16), which this branch was still missing:

• codespell typo ("colume"→"volume" in pkg/util/podvolume/pod_volume_test.go)
• .github/workflows/e2e-test-kind.yaml: build MinIO from the Bitnami Dockerfile instead of the now-unavailable bitnami/minio:2021.6.17-debian-10-r7 tag, bumped to the current 2026/debian-12 path (bitnami/containers reorganizes this per-year)
• Cap the e2e k8s version matrix at v1.35: k8s 1.36+ hits a deterministic BSL-availability race in the BackupsSync e2e suite, unrelated to this branch's diffs

(envtest, linter config, and the test workload image were already fixed on this branch — no changes needed there.)

/kind changelog-not-required

Note

Responses generated with Claude

[coderabbitai]

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 94a5f646-6d8e-4658-909d-249add7bf01f

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

---

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

[openshift-ci]

@kaovilai: The label(s) kind/changelog-not-required cannot be applied, because the repository doesn't have them.

Details

In response to this:

Cherry-pick of velero-io#10001 (already brought upstream to release-1.14 through release-1.18 as velero-io#10428, velero-io#10427, velero-io#10424, velero-io#10425, and velero-io#10426).

Guards several upstream-only GitHub Actions workflows (auto_assign_prs, auto_label_prs, auto_request_review, pr-changelog-check, prow-action, rebase, stale-issues, pr-codespell) with if: github.repository == 'velero-io/velero', so they skip on this fork instead of running here and failing due to missing secrets/config or duplicating this repo's own automation.

pr-filepath-check.yml doesn't exist on this branch, so that guard was dropped (nothing to guard).

/kind changelog-not-required

[!Note]
Responses generated with Claude

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.

[openshift-ci]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, shubham-pampattiwar, sseago

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:

• DOWNSTREAM_OWNERS [kaovilai,shubham-pampattiwar,sseago]

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

[openshift-ci]

PR needs rebase.

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.