Skip to content

Move FabricBot rules to Configuration-As-Code #6538

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 24, 2022

Conversation

RussKie
Copy link
Contributor

@RussKie RussKie commented Jan 24, 2022

Migrates FabricBot automation for the dotnet-api-docs to Config-as-Code. The file is a dump of the automation rules that are currently active and doesn't contain any additional changes.

Similar to dotnet/runtime#62297 and dotnet/dotnet-api-docs#7442.

Microsoft Reviewers: Open in CodeFlow

Migrates FabricBot automation for the dotnet-api-docs to [Config-as-Code](https://microsoft.sharepoint.com/teams/FabricBot/SitePages/Config-as-code.aspx).
The file is a dump of the automation rules that are currently active and doesn't contain any additional changes.
@RussKie RussKie requested a review from a team as a code owner January 24, 2022 01:08
@ghost ghost assigned RussKie Jan 24, 2022
@dreddy-work
Copy link
Member

If it can be edited only in fabric tool, isn't it going to be double the work?

@RussKie
Copy link
Contributor Author

RussKie commented Jan 24, 2022

If it can be edited only in fabric tool, isn't it going to be double the work?

The config can be edited manually, that's the whole point.

@RussKie RussKie merged commit 0b41a88 into dotnet:main Jan 24, 2022
@ghost ghost added this to the 7.0 Preview2 milestone Jan 24, 2022
@RussKie RussKie deleted the Move_FabricBot_rules_to_Config-As-Code branch January 24, 2022 21:29
@RussKie RussKie removed this from the 7.0 Preview2 milestone Jan 25, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Feb 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants