Enable automerge for kubernetes patch updates #109
Merged
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
With optional jobs, we cannot configure required status checks Without this in turn, we cannot use GitHub's automerge feature. Thus, make sure that always one `verify` and one `images` job runs (controller-sharding and webhosting-operator complet each other) so that both job names can be configured as required status checks.
k8s.io/{klog,utils,gengo,kube-openapi,...} are not released together with k8s.io/kubernetes.
Don't include them in the k8s-go group.
1 task
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.
What this PR does / why we need it:
This PR ensures we can use GitHub's automerge feature and enables renovate automerge for k8s patch updates.
Only group k8s go deps that are released together (e.g., don't include
k8s.io/utilsork8s.io/klog).