Moving your GitHub repos from "Microsoft" organization to "Microsoft docs" organization
We are moving all our GitHub repos out of the Microsoft organization. Some of the repos will be moved to VSTS or to an organization in GitHub according to your organization guidelines.
Our goal is to have as many OPS repos in Microsoft docs organization as possible.
- See Microsoft docs guidelines for Microsoft docs organization guidelines.
- See Moving to Microsoft docs tick-tock plan to see all the steps you need to take to move to this organization.
This article only contains details on some of the steps listed in the tick-tock plan.
Details on some of the steps for moving from GitHub Microsoft org to Microsoft docs org
Join the Microsoft docs organization
Be an admin collaborator in your repo
As per GitHub documentation, only collaborator permission will be kept when transferring a repo from one organization to the next. Team permissions will be lost. That means if you are collaborator of the Microsoft repository with admin permission, after transferring, you’re still the admin. However, if you are a member of the team A, even if A has admin permission of the repository, after transferring, you won’t have admin permission any more to the repo in Microsoft docs org.
So make sure that you are a collaborator with amin permissions on your existing repositories before transferring.
- Find your repo in GitHub.
- Click on the Settings tab.
- Click on Collaborators & teams on the left.
- Make sure your GitHub user account is in the Collaborators area as an admin.
Transfer ownership of the repo to Microsoft docs organization
You will do this in the OPS portal. Steps will be added here once we have them.