Action required: migrate or opt-out of migration to GitHub inside Microsoft
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 5/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github
- Domain
- tooling
Research direction
This is an administrative GitHub repository migration notice rather than a source-code task. Read the migration instructions and, if authorized as a repository admin, respond with the specified optin or optout command; it is done when the required RSVP comment is submitted.
Written by the indexing model from the issue text.
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 [email protected]. ✉️
- Post your questions in GitHub inside Microsoft Team in Microsoft Teams. 🗨️
- Dominant language
- Bicep
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
[work-item] adam-adae-worsening-emergence: conform spec.yaml to the specification style contract (REQ-1280)Possibly taken @muse-yamaa-bot claimed this today. Openwork-item
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/servers#5133 ·
Maintainers usually reply within 1 day
-
needs-triage priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#7288 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
carp-lang/carp-emacs#5 ·
-
bug tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day