-
Notifications
You must be signed in to change notification settings - Fork 20
Description
Migrate this repository to GitHub inside Microsoft 🙌
It is now time to migrate this repository to GitHub inside Microsoft a.k.a GitHub Enterprise Cloud with Enterprise Managed User (GHEC EMU).
❗Please make sure to migrate this repository within the alloted period. Failure to migrate after several follow-ups will result in the repository getting automatically archived.
Action
View important prerequisites that you need to be aware of for a smoother migration experience
Managing multiple GitHub accounts in your web broswer
GHEC EMU creates a specific GitHub identity for your internal Microsoft account with the username alias_microsoft. This is a separate identity from any existing GitHub account you may already have and the two accounts are not linked with each other in any way. This is an intentional design decision by GitHub in order to meet the security requirements of its large Enterprise customers. Since GHEC EMU shares the github.com URL with the rest of other GitHub products, it is very important to setup multiple profiles in your Edge web browser; one profile associated with your work account for use with GHEC EMU and another personal profile associated with with your public GitHub identity. See Managing multiple GitHub accounts.
Repository Organization Structure
We create organizations in GHEC EMU based on Service Groups, Organizations and Divisions in Service Tree so you need to make sure that the person performing the migration has existing access to GHEC EMU. See my GHEC EMU organizations.
Instructions
- Open the repository that you are migrating from (source) in your personal profile in Edge.
- In a separate tab or window, open GHEC EMU at https://github.com/enterprises/microsoft in your work profile in Edge.
- Open Start Right at https://aka.ms/startright in a separate tab or window, and follow the instructions to migrate your repository.
What if I'm not ready to migrate yet?
⏰ Snoozing migration reminders
We will send weekly reminders in the form of issue comments until the repository has been successfully migrated.
If you need more time to migrate due to other priorities, you can temporarily snooze the migration reminders.
To snooze the reminders, reply with a comment on this issue containing the following command.
@gimsvc snooze
😕 No longer want to migrate
You can optout of migration if the situation changed for your project. Maybe the repository will now go public, open source, or you require external collaboration.
To opt out, reply with a comment on this issue containing one of theoptout command options below.
@gimsvc optout --reason <staging|collaboration|delete|other>
Example:
@gimsvc optout --reason stagingOptions:
staging: My project will ship as Open Sourcecollaboration: Used for external or 3rd party collaboration with customers, partners, suppliers, etc.delete: This repository will be deleted because it is no longer needed.other: Other reasons not specified
Need help? 🖐️
- Email gim@microsoft.com. ✉️
- Post your questions in GitHub inside Microsoft Team in Microsoft Teams. 🗨️