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
- 1/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github
- Domain
- devops
Research direction
Start with the migration instructions in this issue and confirm that you have repository admin permission. Done means replying with either the documented optin date or optout reason; use the linked GitHub inside Microsoft guidance or the listed support contacts for questions.
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
- Python
- Stars
- 553
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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.
More from microsoft/RPG-ZeroRepo
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/RPG-ZeroRepo#100 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/RPG-ZeroRepo#101 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/RPG-ZeroRepo#5 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
microsoft/RPG-ZeroRepo#3 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/RPG-ZeroRepo#2 · 3 comments ·
All issues in microsoft/RPG-ZeroRepo
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
EvaluationSuite.run fails with default args_for_task and mutates supplied kwargsPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
huggingface/evaluate#825 ·
Maintainers usually reply within 1 day
-
dependencies feature github_actions good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wemake-services/wemake-django-template#3149 ·
Maintainers usually reply within 1 day
-
[request] vsg/1.1.16Openupstream update
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
conan-io/conan-center-index#31142 ·
Maintainers usually reply within 1 day
-
area:core bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day