Publish to hub from a public organization repository
I wanted to publish a public organization's repository to the hub (the account I'm linked to with runpod is admin for this orga), however the orga doesn't show up in the dropdown for adding repos to the hub in the UI (and I couldn't find an API endpoint to do it...). The gh runpod connection for the orga has full rights.
Is this use case unsupported?
6 Replies
Howdy, if the repo doesn't show up in this dropdown at all during the serverless deploy from GitHub option you can go to https://console.runpod.io/user/settings, press "Edit Connection" on GitHub and authorize the org/repo to the app.
the issue is that the organization does not show up in this dropdown, even though I'm a collaborator / admin for the repo
https://console.runpod.io/hub?createListing=true
You will have to use the above linked settings page to authorize the Runpod app to actually read the repo. This may require an owner of the organization to authorize the app. I do note that I can't authorize repos I don't directly own (ie a repo owned by a friend, not an organization) - is that the problem you're seeing as well?
runpod has access to all repos on the orga with the linked account, and the account is an owner of the orga, and admin on each repo.
I can't authorize repos I don't directly own (ie a repo owned by a friend, not an organization)curiously, the dropdown does show other user accounts (where I can select repos I'm a collaborator in)
I'm having a little trouble reproducing, just because I can deploy assets from the orgs I'm in. Let me look around.
I found the root issue, I'll follow up later when we have a solution :fbslightsmile: