Skip to content
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.

Use the Kubeflow DockerHub organization for the GitHub action for issue_triage #67

Merged
merged 3 commits into from
Nov 26, 2019

Conversation

jlewi
Copy link
Contributor

@jlewi jlewi commented Nov 26, 2019


This change is Reviewable

…ue_triage.

* Instead of storing the image in a personal account we should use the kubeflow
  organization.
* Related to kubeflow/code-intelligence#66
@jlewi
Copy link
Contributor Author

jlewi commented Nov 26, 2019

/assign @hamelsmu

@hamelsmu
Copy link
Member

hamelsmu commented Nov 26, 2019

@jlewi you also need to change .github/workflows/triage_issues.yaml

Don't forget to refer to @master branch

While you are at it can you add a more verbose explanation to Issue_Triage/action/README.md so that the community can understand what business rules either add or remove an issue from the Kanban board?

Copy link
Member

@hamelsmu hamelsmu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requested some minor changes

1. Create a workflow like the one above in your repository in the directory

```
.github/workflows/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.github/workflows/
.github/workflows/<your_file_name>.yaml

@hamelsmu
Copy link
Member

hamelsmu commented Nov 26, 2019

@jlewi the push to DockerHub seems to be failing denied: requested access to the resource is denied https://github.com/kubeflow/code-intelligence/commit/5cc4c0a24528440824653b8ccc9fe6db7394fdc4/checks?check_suite_id=328647868#step:3:154

looks like it is still trying to build it as hamelsmu

Nevermind looks like that is trying to run on stale workflow ...hmm but this PR should be triggering a build with each push you do

@hamelsmu hamelsmu self-requested a review November 26, 2019 02:29
@hamelsmu
Copy link
Member

Ohhhhh ! !!!! I know why b/c you are opening this PR from a Fork. Yeah you cannot trigger a build from a Fork because your Fork doesn't have access to secrets and you cannot get access to secrets just by opening a PR

@hamelsmu
Copy link
Member

@jlewi what do you think about my suggested changes above? If you like them please commit and we can merge

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@jlewi
Copy link
Contributor Author

jlewi commented Nov 26, 2019

Don't forget to refer to @master branch
I think I updated all the references

While you are at it can you add a more verbose explanation to Issue_Triage/action/README.md so that the community can understand what business rules either add or remove an issue from the Kanban board?

Done

@jlewi
Copy link
Contributor Author

jlewi commented Nov 26, 2019

Ohhhhh ! !!!! I know why b/c you are opening this PR from a Fork. Yeah you cannot trigger a build from a Fork because your Fork doesn't have access to secrets and you cannot get access to secrets just by opening a PR

This seems like its working as intended. I would only expect the builds of the docker image to be triggered on postsubmit not presubmit. If we trigger on presubmit then people running the action might use unmerged code which seems problematic.

…ion.

* Provide more explanation in the README including instructions for how to deploy.
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@jlewi
Copy link
Contributor Author

jlewi commented Nov 26, 2019

@hamelsmu I think I addressed all your comments.

@hamelsmu
Copy link
Member

/approve
/lgtm

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hamelsmu

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit ea1e599 into kubeflow:master Nov 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants