VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-08 03:27:04 +09:00
Code Activity

FabricBot: Onboarding to GitOps.ResourceManagement because of FabricBot decommissioning (#99169)

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

 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.

* Deleting fabricbot.json

* Update repo documentation that referenced FabricBot

---------

Co-authored-by: dotnet-policy-service[bot] <123482357+dotnet-policy-service[bot]@users.noreply.github.com>
Co-authored-by: Jeff Handley <jeffhandley@users.noreply.github.com>
This commit is contained in:
dotnet-policy-service[bot] 2024-03-06 22:39:50 -08:00 • committed by GitHub
parent 77141aea64
commit ea2532e65c
Signed by: github
GPG key ID: B5690EEEBB952194
5 changed files with 1887 additions and 2947 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.github/CODEOWNERS vendored
View file

@ -112,4 +112,4 @@
# Area ownership and repo automation
/docs/area-owners.* @jeffhandley
/docs/issue*.md @jeffhandley
/.github/fabricbot.json @jeffhandley
/.github/policies/ @jeffhandley @mkArtakMSFT

2938
.github/fabricbot.json vendored
View file

File diff suppressed because it is too large Load diff

1882
.github/policies/resourceManagement.yml vendored Normal file
View file

File diff suppressed because it is too large Load diff

10
docs/infra/automation.md
View file

@ -1,13 +1,9 @@
## Automation
### Fabric Bot
### Policy Service Bot
This repository uses Fabric Bot to automate issue and pull request management. All automation rules are defined in the [`.github/fabricbot.json`](../../.github/fabricbot.json) file.
This repository uses the Policy Service bot to automate issue and pull request management. All automation rules are defined in the [`.github/policies`](../../.github/policies) folder.
#### Notifications
You are welcome to enable notifications for yourself for one or more areas. You will be tagged whenever there are new issues and PR's in the area. You do not need to have commit access for this. To add or remove notifications for yourself, please offer a PR that edits the "mentionees" value for that area. [Here is an example](https://github.com/dotnet/runtime/commit/c28b13f0cf4e2127a74285b65188413ca7e677d4).
#### Other changes
For any other changes, you will need access to the [`Fabric Bot portal`](https://portal.fabricbot.ms/bot/) which is only available to Microsoft employees at present. Ensure you are signed out from the portal, choose "Import Configuration" option and make changes using the editor. It's necessary to use the portal because there is at present no published JSON schema for the configuration format.
You are welcome to enable notifications for yourself for one or more areas. You will be tagged whenever there are new issues and PR's in the area. You do not need to have commit access for this. To add or remove notifications for yourself, please offer a PR that edits the "mentionees" value for that area in the policy YAML file.

2
docs/workflow/ci/triaging-failures.md
View file

@ -8,7 +8,7 @@ stress mode test configuration failures, such as failures in a JIT stress test r
One goal of failure investigation is to quickly route failures to the correct area owner. The ownership of various product areas
is detailed [here](../../area-owners.md). The GitHub auto-tagging bot uses the ownership information
in the file [fabricbot.json](../../../.github/fabricbot.json).
in the file [Policy Service configuration](../../../.github/policies).
## Platform configuration