-
Notifications
You must be signed in to change notification settings - Fork 134
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
Add transfer Issue plugin to Kubeflow repos #2331
Add transfer Issue plugin to Kubeflow repos #2331
Conversation
@andreyvelich: GitHub didn't allow me to request PR reviews from the following users: terrytangyuan, johnugeorge, StefanoFioravanzo, jbottum, rimolive, kimwnasptd, thesuperzapper. Note that only GoogleCloudPlatform members and repo collaborators can review this PR, and authors cannot review their own PRs. 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-sigs/prow repository. |
Hi @andreyvelich. Thanks for your PR. I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@terrytangyuan: changing LGTM is restricted to collaborators 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-sigs/prow repository. |
@andreyvelich we need to ask a googler for review. We should also set up a policy around which situations warrant a repo transfer for an issue, especially for cases where there is ambiguity. In cases where things are very ambiguous (technical discussions covering multiple components), I think we should use And keep those repos for things directly related to their contents. |
Sure. |
@andreyvelich: GitHub didn't allow me to assign the following users: fejta, mpherman2. Note that only GoogleCloudPlatform members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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-sigs/prow repository. |
Why we can't use I feel that it will be really hard to triage issues under |
Additionally, I added We already use this GitHub action in several repos (Pipelines, Katib, Training Operator) to re-trigger GitHub actions using PR comments: https://github.com/estroz/rerun-actions. cc @rimolive |
/test all |
62b40c3
to
a0e3036
Compare
/retest |
@andreyvelich: Cannot trigger testing until a trusted user reviews the PR and leaves an 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-sigs/prow repository. |
/ok-to-test |
I'm good with the changes. |
@thesuperzapper Do you know if I setup the cherrypicker plugin correctly ? |
@rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu Anything you want to add before merging this PR ? |
No other things to add. Thanks @andreyvelich for working in this PR. |
@zijianjoy @chensun @james-jwu @chaodaiG @chases2 @cjwagner @fejta @michelle192837 @mpherman2 Please can you help us to LGTM this PR ? |
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how much work it would take to set up the cherrypicker external-plugin for this Prow instance. If that is something you would like can you please open a separate GitHub issue requesting that?
If you remove the external_plugins section for now I can approve the rest of this PR though.
prow/oss/plugins.yaml
Outdated
events: | ||
- issue_comment | ||
- pull_request | ||
endpoint: http://cherrypicker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no cherrypicker service deployed on this Prow instance so there won't be anything to reach at this endpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks for checking @cjwagner! I will create separate issue and remove it from this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested it with kubeflow/manifests#2837 (comment) and it worked out fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thank you @juliusvonkohout!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreyvelich, cjwagner, terrytangyuan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
0015432
into
GoogleCloudPlatform:master
@andreyvelich: Updated the
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. |
@@ -338,33 +341,11 @@ plugins: | |||
- project # Lets issues be tagged into projects | |||
- size | |||
- skip # Allows cleaning up stale commit statuses | |||
- transfer-issue # Transfer issue to a different repo in the same org. | |||
- trigger # Enable /ok-to-test command to trigger GitHub actions with /rerun-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andreyvelich if my understanding is correct, /ok-to-test
should trigger GitHub Actions after this change. But it didn't.
Do you know if there's anything else that we should do, or is that a bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hbelmiro This plugin just adds ok-to-test
label to the PR after we add this comment: /ok-to-test
.
It doesn't trigger the GitHub actions.
Since we use this action to trigger our action: https://github.com/estroz/rerun-actions, you need to add this comment to trigger the actions:
/rerun-all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see.
The comment made me think that /ok-to-test
would somehow automatically trigger /rerun-all
.
Thank you @andreyvelich.
I added cherrypicker and transfer issue plugins to the Kubeflow repos:
This should help us with Kubeflow repo migration: kubeflow/kubeflow#7549
Also, added
kubeflow/dashboard
repo to the Kubeflow list./hold for review
/cc @rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu