GitHub: Difference between revisions

Jump to navigation Jump to search
114 bytes added ,  29 January 2016
Update xfer instructions: always requires an org admin's assistance
(Highlight importance of setting a team fro admin rights during transfer)
(Update xfer instructions: always requires an org admin's assistance)
Line 28: Line 28:
This is a personal preference.  If you have a large enough project or organization feel free.  We suggest you use the strategies and recommendations here as a model to manage the details.
This is a personal preference.  If you have a large enough project or organization feel free.  We suggest you use the strategies and recommendations here as a model to manage the details.


=== Forking vs Transfering ===
=== Forking vs Transferring ===
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.


Line 35: Line 35:
# If you're not a member of any team, talk to an [[#contact|org admin]].
# If you're not a member of any team, talk to an [[#contact|org admin]].
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
# Choose which teams should be given admin privileges. '''IMPORTANT: choose at least one.''' If you don't chose any you will lose push access to the repo and have to talk to an [[#contact|org admin]].
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on Github (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL.
# Ask an [[#contact|org admin]] to grant team permissions higher than read ('write' and 'admin' are the other choices). (Team maintainers do not have the ability to change a repositories status.)
# Add the appropriate teams to the new Mozilla repo or ask an [[#contact|org admin]] if you lost ownership.
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on Github (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)


=== Do I need to be an owner to create repositories? ===
=== Do I need to be an owner to create repositories? ===
Confirmed users
1,351

edits

Navigation menu