-
Notifications
You must be signed in to change notification settings - Fork 547
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
ci: do not add the ok-to-test
label if there is a conflict
#4557
Conversation
When there is a conflict in merging a PR, the `ok-to-test` label should not be added automatically. This prevents a loop in triggering CI jobs for PRs that might not even build. Signed-off-by: Niels de Vos <ndevos@ibm.com>
d83ff10
to
2b5b298
Compare
ok-to-test
label if there is a conflict
/test ci/centos/k8s-e2e-external-storage/1.28 |
/test ci/centos/mini-e2e-helm/k8s-1.28 |
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/k8s-e2e-external-storage/1.29 |
/test ci/centos/mini-e2e/k8s-1.28 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/mini-e2e-helm/k8s-1.29 |
/test ci/centos/mini-e2e/k8s-1.27 |
/test ci/centos/mini-e2e/k8s-1.29 |
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/upgrade-tests-rbd |
When there is a conflict in merging a PR, the
ok-to-test
label shouldnot be added automatically. This prevents a loop in triggering CI jobs
for PRs that might not even build.
See-also: #4555