Action required: migrate or opt-out of migration to GitHub inside Microsoft

[microsoft-github-policy-service[bot]]

Migrate non-Open Source or non-External Collaboration repositories to GitHub inside Microsoft

In order to protect and secure Microsoft, private or internal repositories in GitHub for Open Source which are not related to open source projects or require collaboration with 3rd parties (customer, partners, etc.) must be migrated to GitHub inside Microsoft a.k.a GitHub Enterprise Cloud with Enterprise Managed User (GHEC EMU).

Action

✍️ Please RSVP to opt-in or opt-out of the migration to GitHub inside Microsoft.

❗Only users with admin permission in the repository are allowed to respond. Failure to provide a response will result to your repository getting automatically archived.🔒

Instructions

Reply with a comment on this issue containing one of the following optin or optout command options below.

✅ Opt-in to migrate

@gimsvc optin --date <target_migration_date in mm-dd-yyyy format>

Example: @gimsvc optin --date 03-15-2023

OR

❌ Opt-out of migration

@gimsvc optout --reason <staging|collaboration|delete|other>

Example: @gimsvc optout --reason staging

Options:

• staging : This repository will ship as Open Source or go public
• collaboration : 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 more help? 🖐️

• Email gim@microsoft.com. ✉️
• Post your questions in GitHub inside Microsoft Team in Microsoft Teams. 🗨️

[wesselb]

@gimsvc optout --reason staging

[microsoft-github-policy-service[bot]]

@wesselb :white_check_mark: you have opted-out of migrating this repository to GitHub inside Microsoft. To continue to protect Microsoft, you should expect to see an issue created in this repository every 120 days to renew your intention whether to migrate or opt-out again.

_{Total execution time: 1.51 seconds}