images/cluster-version-operator: auto_label for merge #1778
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently 4.12 is the dev release, so it only needs lgtm and approved [1]. But eventually 4.12 will hit code-freeze, and then it will also need bugzilla/valid-bug and staff-eng-approved [2]. And eventually it will be a generally available release, and then it will need approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, and lgtm [3]. The CVO is very flexible about Go versions and whatnot, so we don't need any of these sign-offs for CI-alignment pull requests. With this commit, we add all the labels we'll need to merge at any stage of the 4.12 lifecycle. And hopefully the same configuration will propagate into 4.13 once we get release branches here for that. [1]: https://github.com/openshift/release/blob/7114512b31971dcfe83454a40ed77f8881cecc73/core-services/prow/02_config/openshift/cluster-version-operator/_prowconfig.yaml#L57-L62 [2]: https://github.com/openshift/release/blob/7114512b31971dcfe83454a40ed77f8881cecc73/core-services/prow/02_config/openshift/cluster-version-operator/_prowconfig.yaml#L40-L47 [3]: https://github.com/openshift/release/blob/7114512b31971dcfe83454a40ed77f8881cecc73/core-services/prow/02_config/openshift/cluster-version-operator/_prowconfig.yaml#L3-L30
|
@wking: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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/test-infra repository. |
Build #1 |
This was referenced Sep 20, 2023
Closed
Merged
This was referenced Sep 6, 2024
This was referenced Sep 18, 2024
This was referenced Sep 27, 2024
This was referenced Oct 7, 2024
This was referenced Oct 14, 2024
This was referenced Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently 4.12 is the dev release, so it only needs
lgtmandapproved. But eventually 4.12 will hit code-freeze, and then it will also needbugzilla/valid-bugandstaff-eng-approved. And eventually it will be a generally available release, and then it will needapproved,backport-risk-assessed,bugzilla/valid-bug,cherry-pick-approved, andlgtm. The CVO is very flexible about Go versions and whatnot, so we don't need any of these sign-offs for CI-alignment pull requests. With this commit, we add all the labels we'll need to merge at any stage of the 4.12 lifecycle. And hopefully the same configuration will propagate into 4.13 once we get release branches here for that.