search

heroku / heroku-connect-plugin

CLI plugin for Heroku Connect (experimental)
Apache License 2.0
23 stars 8 forks source link

add heroku user to plugin #2

Closed jdx closed 8 years ago

jdx commented 8 years ago

just in case someone needs to push a patch, it would be good to add the shared heroku account as a collab: https://www.npmjs.com/~heroku

gulopine commented 8 years ago

Now that we have a Heroku org, I'd like to move this into org ownership, but I'm not clear on how to do so. Do you have any guidance there?

jdx commented 8 years ago

I think you have to submit a support ticket. Ugh. On Wed, Apr 6, 2016 at 2:42 PM Marty Alchin notifications@github.com wrote:

Now that we have a Heroku org, I'd like to move this into org ownership, but I'm not clear on how to do so. Do you have any guidance there?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/heroku/heroku-connect-plugin/issues/2#issuecomment-206583646

gulopine commented 8 years ago

I've submitted a request with npm, I'll update this ticket once I've heard something.

gulopine commented 8 years ago

Thanks for emailing. Are you an admin member of the heroku org? If so, you can add the package to the heroku org by clicking on the team you want it on, then "add packages", then "populate from personal packages". You can always change a developer to "team admin" by removing them from the org and re-adding as team admin.

jdx commented 8 years ago

I'm not, that's @rcansley

rcansley commented 8 years ago

hi @gulopine - I've made you a Team Admin. Let me know if that works for ya.

@dickeyxxx I have shared the itops (org admin) creds with you in Lastpass. Feel free to go around IT for admin stuff going forward!

gulopine commented 8 years ago

With some help from @scottpersinger, we've managed to move the package into the heroku org. Lots of people are now marked as owners and should be able to manage it as necessary.