Skip to content
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

Apply the needs-upstream label for PRs with vendor changes #214

Merged
merged 1 commit into from
Oct 14, 2017

Conversation

stevekuznetsov
Copy link
Contributor

Signed-off-by: Steve Kuznetsov skuznets@redhat.com

/cc @deads2k @Kargakis @smarterclayton

Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 4, 2017
@deads2k
Copy link
Contributor

deads2k commented Oct 4, 2017

@soltysh can you explain how you would use this for blocking upstream pulls during a kube rebase?

@stevekuznetsov
Copy link
Contributor Author

We can expand the submit-queue's negative label list to include it (think the opposite of the kind/bug flow)

@0xmichalis
Copy link
Contributor

We will get it for free with tide but yeah, in the meantime we can add it in the submit queue.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2017
@0xmichalis
Copy link
Contributor

It still sucks that the queue will need to restart for the label change.

@stevekuznetsov
Copy link
Contributor Author

What I wanted to do, which would not be webhook based, was use a graphql query and commenter bot to just add /hold on to the prs...

@0xmichalis
Copy link
Contributor

SGTM. We should run something similar when we add new blocking presubmits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
4 participants