Action required: self-attest your goal for this repository

[microsoft-github-policy-service]

It's time to review and renew the intent of this repository

An owner or administrator of this repository has previously indicated that this repository can not be migrated to GitHub inside Microsoft because it is going public, open source, or it is used to collaborate with external parties (customers, partners, suppliers, etc.).

Action

👀 ✍️ In order to keep Microsoft secure, we require repository owners and administrators to review this repository and regularly renew the intent to either opt-in or opt-out of migration to GitHub inside Microsoft which is specifically intended for private or internal projects.

❗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

❌ Opt-out of migration

If this repository can not be migrated to GitHub inside Microsoft, you can opt-out of migration by replying with a comment on this issue containing one of the following optout command options below.

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

Example: @gimsvc optout --reason staging

Options:

• staging : My project will ship as Open Source
• 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

✅ Opt-in to migrate

If the circumstances of this repository has changed and you decide that you need to migrate, then you can specify the optin command below. For example, the repository is no longer going public, open source or require external collaboration.

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

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

Click here for more information about optin and optout command options and examples

Opt-in

@gimsvc optin --date <target_migration_date>

When opting-in to migrate your repository, the --date option is required followed by your specified migration date using the format: mm-dd-yyyy

@gimsvc optin --date 03-15-2023

Opt-out

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

When opting-out of migration, you need to specify the --reason.

• staging
  • My project will ship as Open Source
• 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

Examples:

@gimsvc optout --reason staging

@gimsvc optout --reason collaboration

@gimsvc optout --reason delete

@gimsvc optout --reason other

Need more help? 🖐️

• Email [email protected]. ✉️
• Post your questions in GitHub inside Microsoft Team in Microsoft Teams.

[microsoft-github-policy-service]

👋 owners of private and internal repositories are required to self-attest your project goals every 120 days. If you no longer have plans to make the repository public or if you are no longer collaborating with 3rd parties (customers, partners, etc.), please migrate this repository to GitHub inside Microsoft. Otherwise, you can opt-out of migration. Please see the issue description ☝️ for details. Failure to provide a response after 4 more reminders will result in the repository getting archived.

[microsoft-github-policy-service]

⚠️ Please provide a response. Failure to provide a response after 3 more reminders will result in the repository getting archived.

[microsoft-github-policy-service]

⚠️ Please provide a response. Failure to provide a response after 2 more reminders will result in the repository getting archived.

[microsoft-github-policy-service]

⚠️ Please provide a response. Failure to provide a response after 1 more reminders will result in the repository getting archived.

[microsoft-github-policy-service]

⚠️ This repository will be archived because a response was expected but was not provided within the expected timeframe after several follow-ups. If you need to continue to use this repository, repository administrators can unarchive it. After successfully unarchiving, repository administrators must provide a response to prevent the repository from getting archived again.