Skip to content

Conversation

@microsoft-github-policy-service
Copy link
Contributor

Add prIssueManagement.yml to onboard repo to GitOps.ResourceManagement as FabricBot replacement

Owners of the FabricBot configuration should have received email notification. The same information contained in the email is published internally at: https://aka.ms/gim/fabricbot. Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html

Please review and merge this PR to complete the process of onboarding to the new service.

…t as FabricBot replacement

Owners of the FabricBot configuration should have received email notification. The same information contained in the email is published internally at: https://aka.ms/gim/fabricbot. Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html

Please review and merge this PR to complete the process of onboarding to the new service.
@microsoft-github-policy-service
Copy link
Contributor Author

Action Required

On August 8, Fabric Bot will be turned off and Issues and PR's in this repository will stop receiving the automations it provides. Merging this PR prior to that date will ensure that the automations you have configured will continue without interruption. Please review and merge this PR as soon as possible.

See aka.ms/gim/fabricbot for more information

@ejizba
Copy link
Contributor

ejizba commented Jul 27, 2023

/azp run

@azure-pipelines
Copy link

No commit pushedDate could be found for PR 702 in repo Azure/azure-functions-nodejs-worker

@ejizba ejizba merged commit e23b5f7 into v3.x Jul 27, 2023
@ejizba ejizba deleted the onboarding-prIssueManagement branch July 27, 2023 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants