The dotnet/fabricbot-config repo is where we have generation of these fabricbot config files scripted out. We include the generated files in that repository for the sole purpose of reviewing the PRs there to illustrate they have the desired effect. But those generated files do not affect any of the actual configurations.
In dotnet/dotnet-api-docs, dotnet/machinelearning, and especially dotnet/runtime, there are non-generated fabricbot config rules as well. Running the generate.ps1 script from dotnet/fabricbit-config also edits the generated files in the peer repositories that are affected, merging the generated and non-generated configs together. Committing the fabricbot.json files into the dotnet/dotnet-api-docs, dotnet/machinelearning, and dotnet/runtime repositories actually updates the issue/PR automation rules.
The dotnet/fabricbot-config repo is where we have generation of these fabricbot config files scripted out. We include the generated files in that repository for the sole purpose of reviewing the PRs there to illustrate they have the desired effect. But those generated files do not affect any of the actual configurations.
In dotnet/dotnet-api-docs, dotnet/machinelearning, and especially dotnet/runtime, there are non-generated fabricbot config rules as well. Running the
generate.ps1script from dotnet/fabricbit-config also edits the generated files in the peer repositories that are affected, merging the generated and non-generated configs together. Committing the fabricbot.json files into the dotnet/dotnet-api-docs, dotnet/machinelearning, and dotnet/runtime repositories actually updates the issue/PR automation rules.