🌱 standardizing approach for required-tests-with-occasional-overrides

[grokspawn]

Description

Updates the go-ver-diff and crd-diff tests to follow a standardized approach where they examine labels on the PR to override against failures. This provides the ability for good override capture for required tests (which we want occasionally to override) in a context where having GH handles the tests and prow handles the merges doesn't include the ability for prow to override GH tests.
In this case, creation and application of a label of the form <workflow-name>-override on the PR will allow the test to fail but record the override for prosperity.

Reviewer Checklist

• API Go Documentation
• Tests: Unit Tests (and E2E Tests, if appropriate)
• Comprehensive Commit Messages
• Links to related GitHub Issue(s)

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	54109b1
🔍 Latest deploy log	https://app.netlify.com/projects/olmv1/deploys/695d8af7681ca50008dc5c3c
😎 Deploy Preview	https://deploy-preview-2431--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR standardizes the approach for handling test overrides in required CI workflows by moving the override logic from shell scripts to GitHub Actions workflow steps. The change enables users to apply labels like go-verdiff-override or crd-diff-override to PRs to bypass test failures while maintaining a record of the override.

Key Changes:

• Moved override checking logic from bash scripts to GitHub Actions workflow files
• Implemented a two-step pattern: run the test with error continuation, then check for override labels
• Standardized the override label naming convention to <workflow-name>-override

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
hack/tools/check-go-version.sh	Removed override label checking logic and LABELS environment variable handling from the shell script
.github/workflows/go-verdiff.yaml	Added separate step for checking override labels with proper error handling and environment configuration
.github/workflows/crd-diff.yaml	Added override label checking step following the same pattern as go-verdiff workflow

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tmshort]

/lgtm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.96%. Comparing base (bcb3d07) to head (54109b1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #2431 +/- ##
==========================================
- Coverage 73.05% 72.96% -0.10% 
==========================================
Files 100 100 Lines 7641 7641 ==========================================
- Hits 5582 5575 -7 - Misses 1623 1630 +7 
Partials 436 436 

Flag	Coverage Δ
e2e	46.85% <ø> (ø)
experimental-e2e	48.49% <ø> (-0.26%)	⬇️
unit	57.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[oceanc80]

/lgtm

[rashmigottipati]

/lgtm

[grokspawn]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, rashmigottipati

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:

• .github/OWNERS [grokspawn]
• hack/OWNERS [grokspawn]

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