Skip to content

{CI} Preserve squad mentions during service contact sync - #10347

Merged
ZelinWang (wangzelin007) merged 1 commit into
Azure:mainfrom
wangzelin007:fix/preserve-squad-contact-sync
Sep 16, 2026
Merged

ZelinWang (wangzelin007) merged 1 commit into
Azure:mainfrom
wangzelin007:fix/preserve-squad-contact-sync

Conversation

@wangzelin007

@wangzelin007 ZelinWang (wangzelin007) commented Sep 16, 2026

Copy link
Copy Markdown
Member

🤖 PR Validation — ️✔️ All clear

Breaking Changes
️✔️ None

Related command

N/A - internal service-contact synchronization pipeline only.

Description

The service contact wiki does not contain the squad teams maintained by squad mapping. Rebuilding the triage rules from that wiki currently removes those teams and produces recurring removal PRs, such as #10306.

  • Preserve existing mentionees matching ^Azure/act-[a-z0-9-]+-squad$ on the corresponding service label.
  • Continue synchronizing ordinary contacts and service additions/removals from the wiki; other Azure/... teams are not exempted.
  • Avoid duplicate squad mentions and keep repeated synchronization idempotent.
  • Add offline regression coverage for matching boundaries, per-service preservation, normal contact updates, and repeated runs.

Testing guide

Requires Python with pytest and PowerShell 7 (pwsh) on PATH.

python -m pytest scripts\automation\tests\test_service_contacts.py -q -p no:cacheprovider

The 20 targeted tests pass. An offline comparison of the checked-in policy confirms that omitting squads from the wiki leaves all 260 service rules unchanged and retains all 161 squad mentions. A fixture from PR #10306 also retains its ordinary contact changes without removing squads.

No live wiki access, pipeline execution, generated policy edits, extension version changes, or release notes are needed for this fix.

Related PR

Companion Azure CLI fix: Azure/azure-cli#34087.

Keep existing Azure/act-...-squad mentionees when rebuilding service routing from the contact wiki. Add offline regression coverage for regular contact updates, exact team matching, and idempotent synchronization.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ae380b25-034e-4550-9636-fa1443bc8205
Copilot AI lite review requested due to automatic review settings September 16, 2026 00:25
@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi ZelinWang (@wangzelin007),
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in pyproject.toml (or setup.py, if the extension has not migrated yet) as well.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No unresolved blocking issues were identified, and targeted regression coverage is included.

Pull request overview

Preserves squad mentions during wiki-driven service-contact synchronization while retaining normal contact updates.

Changes:

  • Adds squad preservation and deduplication logic.
  • Adds offline regression coverage for synchronization behavior.
File summaries
File Description
scripts/automation/ParseServiceContactsList.ps1 Preserves matching squad mentions during synchronization.
scripts/automation/tests/test_service_contacts.py Adds offline synchronization regression tests.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@yonzhan

Copy link
Copy Markdown
Collaborator

CI

@wangzelin007
ZelinWang (wangzelin007) merged commit 073362f into Azure:main Sep 16, 2026
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants