NO-ISSUE: Update verify_commits.sh to use main branch

[tmshort]

We now use the main branch. The CI call to this was changed to use main, but we might as well make it the default since make verify can be run locally.

[openshift-ci-robot]

@tmshort: This pull request explicitly references no jira issue.

In response to this:

We now use the main branch. The call to this was changed to use main, but we might as well make it the default since make verify can be run locally.

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.

[tmshort]

The error being seen:

/Library/Developer/CommandLineTools/usr/bin/make verify-commits
./scripts/verify_commits.sh  # see https://github.com/kubernetes/test-infra/blob/master/prow/jobs.md#job-environment-variables
fatal: bad revision '^master'
[2025-10-17T12:18:05-0400]: detected 0 commit(s) to verify
Successfully validated all commits

[grokspawn]

Also update 108?

Looks like not, because if I do that I get an error, whereas 108 saying 'master' appears to grab the correct list of commits to evaluate.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

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

The pull request process is described here

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS [tmshort]

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

[tmshort]

And verify-deps is failing? This has nothing to do with that‽‽

[grokspawn]

This looks like a change in openshift/api dependency checking, and some "contagious" version. Great that it is "discovered" instead of "advertised".

[grokspawn]

Fixed here and needing to come downstream to resolve this, I guess.

Additional conversation which was discovered only after another team encountered the new "antibiotics": https://redhat-internal.slack.com/archives/C07RDCVEYJG/p1760624199090789

[jupierce]

/override ci/prow/verify-deps

[openshift-ci]

@jupierce: Overrode contexts on behalf of jupierce: ci/prow/verify-deps

In response to this:

/override ci/prow/verify-deps

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.

[grokspawn]

/retest-required

[tmshort]

/retest

[tmshort]

/retest-required

[openshift-ci]

@tmshort: The following tests 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/e2e-gcp-olm	dd29742	link	true	/test e2e-gcp-olm
ci/prow/okd-scos-e2e-aws-ovn	dd29742	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.