You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is really a pain to manage because there is no easy way to make multiple people administrators of this account.
Using a GitHub App is also much better for programmatic modification.
We can easily create GitHub Apps within our existing Kubeflow GitHub org.
GitHub Apps however can't "own" repositories. So when our CI/CD bot opens up PRs to update kubeflow/manifests where should it create those new branches?
Possible options
Use a branch on kubeflow/manifests
Create a new GitHub org "kubeflow-bots" and put forks of any repos needed by bots there.
I think I prefer the second option.
Using a fork seems cleaner then polluting kubeflow repos with a bunch of auto created PRs
Using separate forks seems like it would require giving the bot less privileges
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.
Right now we use a user account
https://github.com/kubeflow-bot
as a robot account.
This is really a pain to manage because there is no easy way to make multiple people administrators of this account.
Using a GitHub App is also much better for programmatic modification.
We can easily create GitHub Apps within our existing Kubeflow GitHub org.
GitHub Apps however can't "own" repositories. So when our CI/CD bot opens up PRs to update kubeflow/manifests where should it create those new branches?
Possible options
I think I prefer the second option.
The text was updated successfully, but these errors were encountered: