Skip to content

Allow override of go-verdiff result via label #3592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 5, 2025

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Jun 4, 2025

Rather than disabling the go-verdiff CI to allow it to pass when there is a legitimate golang version change, use a label to override the test results.

The label is (override-go-verdiff).

See: operator-framework/operator-controller#1964

Description of the change:

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@openshift-ci openshift-ci bot requested review from ankitathomas and grokspawn June 4, 2025 14:12
grokspawn
grokspawn previously approved these changes Jun 4, 2025
@grokspawn grokspawn added this pull request to the merge queue Jun 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jun 4, 2025
@tmshort tmshort added this pull request to the merge queue Jun 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jun 4, 2025
@tmshort tmshort added this pull request to the merge queue Jun 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jun 4, 2025
@tmshort tmshort added this pull request to the merge queue Jun 5, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jun 5, 2025
@grokspawn grokspawn added this pull request to the merge queue Jun 5, 2025
Comment on lines 6 to 8
push:
workflow_dispatch:
merge_group:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This removes support for the merge queue, which is still live for this repo. Please re-add these lines.

Rather than disabling the go-verdiff CI to allow it to pass when
there is a legitimate golang version change, use a label to override
the test results.

The label is `(override-go-verdiff)`.

Signed-off-by: Todd Short <[email protected]>
@tmshort tmshort force-pushed the update-go-ver-diff branch from 163dede to 6f44358 Compare June 5, 2025 14:27
@grokspawn grokspawn removed this pull request from the merge queue due to a manual request Jun 5, 2025
@grokspawn grokspawn enabled auto-merge June 5, 2025 14:29
@grokspawn grokspawn added this pull request to the merge queue Jun 5, 2025
Merged via the queue into operator-framework:master with commit e1f5f6b Jun 5, 2025
13 checks passed
@tmshort tmshort deleted the update-go-ver-diff branch June 5, 2025 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants