{CI} Sync squad mapping into resourceManagement.yml by azure-powershell-bot · Pull Request #29905 · Azure/azure-powershell

azure-powershell-bot · 2026-07-27T16:52:51Z

Description

This PR synchronizes squad labels, reviewers and mentionees into resourceManagement.yml based on the Squad Mapping wiki.

Checklist

Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
SHOULD make the title of PR clear and informative, and in the present imperative tense.
SHOULD update ChangeLog.md file(s) appropriately
- For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
- A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
- Should not change ChangeLog.md if no new release is required, such as fixing test case only.
SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
- Create new module from scratch
- Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
- Create new resource type which name doesn't use module name as prefix
- Have design question before implementation
SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
SHOULD have proper test coverage for changes in pull request.
SHOULD NOT introduce breaking changes in Az minor release except preview version.
SHOULD NOT adjust version of module manually in pull request

azure-pipelines · 2026-07-27T16:53:04Z

Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run.

Copilot

Pull request overview

This PR updates the GitHub policy routing configuration in .github/policies/resourceManagement.yml to synchronize squad labels/mentionees/reviewers with the current squad mapping source, ensuring issues/PRs get routed to the correct squads.

Changes:

Updated multiple “Service Attention” routing rules to use the correct ACT squad teams (e.g., experience enablement / observability / quality productivity) for mentions and labels.
Updated “[Squad Auto-Assign]” PR label-based review requests to use Azure/<team> reviewer identifiers.

Comments suppressed due to low confidence (27)

.github/policies/resourceManagement.yml:896

This route now adds act-observability-squad twice and lists Azure/act-observability-squad twice under mentionees, which can result in duplicate mentions and redundant label operations. Keep only one entry of each.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:974

This route now duplicates the same squad in mentionees and applies the same label twice. This can generate duplicate notifications and redundant label calls; dedupe both lists.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:997

Azure/act-experience-enablement-squad and act-experience-enablement-squad are both duplicated here (mentionees + addLabel). This is noisy and can lead to duplicate mentions; keep single entries.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1021

The same team is listed twice in mentionees and the same label is added twice. Deduplicating avoids duplicate notifications and redundant operations.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1043

This section duplicates the same squad in mentionees and duplicates the addLabel action. This can cause double-mentions and extra label calls; keep only one of each.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1066

The same squad/team and label are duplicated (two identical mentionees + two identical addLabel actions). Deduplicate to avoid duplicate routing noise.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1090

Duplicate Azure/act-experience-enablement-squad entries in mentionees and duplicate addLabel actions will result in double-mentions and extra label operations. Remove the duplicates.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1114

This route now repeats the same squad in mentionees and adds the same label twice. Deduplicate to avoid duplicate notifications and redundant label calls.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1136

The same squad appears twice in mentionees and the label is applied twice. Keeping a single entry avoids duplicate mentions/operations.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1158

Azure/act-experience-enablement-squad is duplicated in mentionees and addLabel is duplicated. This can double-mention the team and issue redundant label requests; dedupe.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1181

This block duplicates the same squad in mentionees and duplicates the addLabel action. Deduplicate to avoid duplicate notifications and redundant calls.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1203

This route lists the same team twice in mentionees and adds the same label twice. Remove duplicates to avoid double-mentions and redundant labeling.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1225

Azure/act-experience-enablement-squad and act-experience-enablement-squad are duplicated here (mentionees + addLabel). Deduplicate to avoid duplicate notifications and redundant API calls.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1248

Duplicate mentionees and duplicate addLabel actions will cause duplicate mentions/redundant label operations. Keep a single squad entry and a single label action.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1271

The same squad is included twice in mentionees and the label is added twice. This can double-notify the team and make redundant API calls; dedupe both.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1293

This route now duplicates the squad entry in mentionees and duplicates the same addLabel action. Remove the duplicates to avoid double-mentions and redundant label calls.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1315

There are duplicate entries for the same squad (mentionees + addLabel). This can create duplicate notifications and redundant operations; keep single entries.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1340

This route duplicates the same team entry in mentionees and adds the same label twice. Deduplicate to avoid double-mentions and redundant API calls.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:1422

This route duplicates the same squad in mentionees and duplicates the addLabel action. This can lead to duplicate notifications and redundant label API calls; keep single entries.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:2445

Azure/act-observability-squad is listed twice in mentionees and the label is added twice. Deduplicate to avoid double-mentions and redundant labeling calls.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:2467

The same squad is duplicated under mentionees and addLabel is duplicated. This can cause duplicate notifications and redundant label operations; keep only one entry of each.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:2715

This route repeats Azure/act-observability-squad in mentionees and adds the same label twice. Removing duplicates avoids double-mentions and redundant label calls.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:2807

The same squad/team and label are duplicated here (two identical mentionees + two identical addLabel actions). Deduplicate to avoid duplicate mentions and redundant labeling operations.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

.github/policies/resourceManagement.yml:3570

This block duplicates the same team in mentionees and duplicates the addLabel action. This can cause double notifications and redundant label requests; keep only one entry.

        - addLabel:
            label: act-quality-productivity-squad
        - addLabel:
            label: act-quality-productivity-squad

.github/policies/resourceManagement.yml:4527

This route repeats the same squad in mentionees and applies the same label twice. Deduplicate to avoid double-mentioning the team and redundant label operations.

        - addLabel:
            label: act-observability-squad
        - addLabel:
            label: act-observability-squad

.github/policies/resourceManagement.yml:4568

This block duplicates Azure/act-codegen-extensibility-squad in mentionees and duplicates the addLabel action. Deduplicate to avoid double notifications and redundant label operations.

        - addLabel:
            label: act-codegen-extensibility-squad
        - addLabel:
            label: act-codegen-extensibility-squad

.github/policies/resourceManagement.yml:4878

The same squad is listed twice in mentionees and the same label is added twice. This can double-mention the team and make redundant label calls; dedupe both.

        - addLabel:
            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad

        - addLabel:
-            label: act-codegen-extensibility-squad
+            label: act-experience-enablement-squad
        - addLabel:
            label: act-experience-enablement-squad


Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (4)

.github/policies/resourceManagement.yml:870

The mentionees list includes the same team twice, and the then block also adds the same squad label twice. This can cause duplicate @mentions in the reply template output and redundant label operations; it looks like the sync inserted a duplicate entry.

            - sgellock
            - Azure/act-experience-enablement-squad
            - Azure/act-experience-enablement-squad
            replyTemplate: Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc ${mentionees}.
            assignMentionees: False

.github/policies/resourceManagement.yml:891

This routing block duplicates the same squad team in mentionees and duplicates the same addLabel action. That can result in double-notifications and unnecessary repeated label operations.

            mentionees:
            - hirenshah1
            - Azure/act-observability-squad
            - Azure/act-observability-squad
            replyTemplate: Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc ${mentionees}.

.github/policies/resourceManagement.yml:3565

The same squad team is listed twice under mentionees and the same label is added twice. This will generate redundant notifications/operations; please de-duplicate to a single entry/action.

            mentionees:
            - audunn
            - Azure/act-quality-productivity-squad
            - Azure/act-quality-productivity-squad
            replyTemplate: Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc ${mentionees}.

.github/policies/resourceManagement.yml:4563

This rule lists Azure/act-codegen-extensibility-squad twice under mentionees and repeats the same addLabel action. That can lead to duplicate mentions in the bot reply and unnecessary repeated label operations.

            mentionees:
            - azureSQLGitHub
            - Azure/act-codegen-extensibility-squad
            - Azure/act-codegen-extensibility-squad
            replyTemplate: Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc ${mentionees}.

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

.github/policies/resourceManagement.yml:868

This block now includes duplicate entries for the same squad in both mentionees and addLabel (the act-experience-enablement squad appears twice). This can lead to redundant/duplicate mentions and label operations; keep only one occurrence of each.

        - mentionUsers:
            mentionees:
            - sgellock
            - Azure/act-experience-enablement-squad
            - Azure/act-experience-enablement-squad

.github/policies/resourceManagement.yml:890

This rule duplicates the same squad in mentionees and repeats the same addLabel step twice. It’s redundant and may cause duplicate notifications; remove the extra mentionee and one of the duplicated label actions.

        - mentionUsers:
            mentionees:
            - hirenshah1
            - Azure/act-observability-squad
            - Azure/act-observability-squad

.github/policies/resourceManagement.yml:4562

This rule contains duplicate mentionees entries for the same team and repeats the same addLabel twice. Even if downstream deduplicates, keeping duplicates in config increases noise and can result in duplicate mentions/operations; remove the duplicates here (and in other blocks updated similarly in this PR).

        - mentionUsers:
            mentionees:
            - azureSQLGitHub
            - Azure/act-codegen-extensibility-squad
            - Azure/act-codegen-extensibility-squad

azure-powershell-bot requested review from NoriZC, VeryEarly and isra-fel as code owners July 27, 2026 16:52

Copilot AI review requested due to automatic review settings July 27, 2026 16:52

azure-powershell-bot requested review from naga-nandyala, necusjz and wangzelin007 as code owners July 27, 2026 16:52

Copilot started reviewing on behalf of azure-powershell-bot July 27, 2026 16:53 View session

Copilot AI reviewed Jul 27, 2026

View reviewed changes

Comment thread .github/policies/resourceManagement.yml

Comment on lines 871 to 874

- addLabel:

label: act-codegen-extensibility-squad

label: act-experience-enablement-squad

- addLabel:

label: act-experience-enablement-squad

azure-powershell-bot force-pushed the internal/sync-squad-mapping branch from 2e335a6 to 7741a7f Compare July 28, 2026 16:42

Copilot AI review requested due to automatic review settings July 28, 2026 16:42

Copilot started reviewing on behalf of azure-powershell-bot July 28, 2026 16:42 View session

Copilot AI reviewed Jul 28, 2026

View reviewed changes

Sync squad mapping to resourceManagement.yml

a545cba

azure-powershell-bot force-pushed the internal/sync-squad-mapping branch from 7741a7f to a545cba Compare July 30, 2026 16:46

Copilot AI review requested due to automatic review settings July 30, 2026 16:46

Copilot started reviewing on behalf of azure-powershell-bot July 30, 2026 16:47 View session

Copilot AI reviewed Jul 30, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

{CI} Sync squad mapping into resourceManagement.yml - #29905

{CI} Sync squad mapping into resourceManagement.yml#29905
azure-powershell-bot wants to merge 1 commit into
mainfrom
internal/sync-squad-mapping

azure-powershell-bot commented Jul 27, 2026

Uh oh!

azure-pipelines Bot commented Jul 27, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

azure-powershell-bot commented Jul 27, 2026

Description

Checklist

Uh oh!

azure-pipelines Bot commented Jul 27, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants