Adds doc for how to transfer ownership of a gem #578
Conversation
binford2k
left a comment
binford2k
left a comment
There was a problem hiding this comment.
do we want to add information about configuring CI to this guide, as in voxpupuli/metadata-json-lint#163?
@bastelfreak might have opinions here
|
I was going to make another doc about transferring a project and all the steps. This is just scoped to gem transfers on ruby gems. |
logicminds
force-pushed
the
transfer_gem
branch
from
e498306 to
c5f5d66
Compare
|
|
||
| ## Adding Owners to an Existing Gem | ||
|
|
||
| To add owners to an existing gem head over to RubyGems.org website. |
There was a problem hiding this comment.
Should we document the CLI command? gem owner -a voxpupuli GEM
It has the benefit that we don't need to specify the email address publicly.
There was a problem hiding this comment.
I explicitly left that out because the UI seems like it has some better safeguards. I just wanted to give a single way to do it. Using the cli also means you have an API key that hasn't expired as well and is scoped to adding owners.
There was a problem hiding this comment.
the website will accept the username too
3 participants
This adds a short doc on how to transfer a gem to VoxPupuli