Repository navigation
Update SDK breaking-change and release-plan automation approver lists - #47121
Conversation
|
Azure Pipelines: Successfully started running 8 pipeline(s). 5 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: JialinHuang803 <139532647+JialinHuang803@users.noreply.github.com>
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
|
Copilot Please extend this PR with this user-requested change: in
Preserve every existing entry, avoid duplicates, and follow the existing formatting. Keep the original addition of |
|
Copilot User correction to the preceding request: the last handle is |
Co-authored-by: JialinHuang803 <139532647+JialinHuang803@users.noreply.github.com>
Added the eight requested handles to |
Co-authored-by: JialinHuang803 <139532647+JialinHuang803@users.noreply.github.com>
Corrected the allowlist entry to |
Summary
Update two protected-label allowlists in
.github/protected-labels.yml. This is a repository automation configuration change, not an API specification or SDK emitter configuration change.JialinHuang803to the sharedsdk-breaking-change-approversYAML anchor. Existing aliases continue to use this roster for SDK breaking-change approval and suppression-approval labels.ArcturusZhang,weidongxu-microsoft,XiaofeiCao,ChenxiJiang333,kazrael2119,v-jiaodi,v-xuto, andlive1206toSkip-ReleasePlan-Automation.Preserve all existing entries and label aliases. No global-approver permissions, other authorization policies, API specifications, or SDK generation settings are changed.