microsoft / microsoft/TechLab-Configure-Teams-Direct-Routing
Action required: migrate or opt-out of migration to GitHub inside Microsoft
@LearningTree01 y travaille déjà.
Depuis le 16/6/2026.
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 0
- Forks
- 0
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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 stagingOptions:
staging: This repository will ship as Open Source or gopubliccollaboration: 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. 🗨️
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.