{Doc} Update scrum-master's-playbook.md#33101
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @yanzhudd, |
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull request overview
Updates the Scrum Master playbook documentation to reflect current ongoing responsibilities and provide an updated Batched CI reference/screenshot.
Changes:
- Removes the “weekly sync meeting” responsibility line.
- Adds a direct link to Batched CI and updates the embedded screenshot to a new image asset.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| doc/scrum-master's-playbook.md | Removes an outdated responsibility, updates Batched CI link, and points to the new screenshot asset. |
| doc/assets/batched-ci-pipeline.png | Adds a new Batched CI pipeline screenshot referenced by the playbook. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - Attend office hours held on Tuesday and Friday. | ||
| - Join this [channel](https://teams.microsoft.com/l/chat/19:e4bb31fd84ab4f2f9375ad848e8a80fa@thread.v2/conversations?context=%7B%22contextType%22%3A%22chat%22%7D). If there is any topic related to CLI requested, make sure to join the call. Request product manager to add you to the meeting series. | ||
| - Monitor Batched CI on a regular basis: | ||
| - Monitor [Batched CI](https://dev.azure.com/azclitools/public/_build?definitionId=32&_a=summary&repositoryFilter=12&branchFilter=487%2C487%2C487) on a regular basis: |
There was a problem hiding this comment.
The Batched CI link includes repositoryFilter/branchFilter query params, which makes the URL longer and potentially brittle if those filter IDs change. Consider linking to the pipeline summary using only the definitionId (similar to other pipeline links in this document) and letting readers apply filters in the UI if needed.
| - Monitor [Batched CI](https://dev.azure.com/azclitools/public/_build?definitionId=32&_a=summary&repositoryFilter=12&branchFilter=487%2C487%2C487) on a regular basis: | |
| - Monitor [Batched CI](https://dev.azure.com/azclitools/public/_build?definitionId=32&_a=summary) on a regular basis: |
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.