-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Update the PR spec template with information about how to get help from the ARM API reviewer in the absence of the PR assignee #27362
Conversation
…he ARM API reviewer
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Validation Report
|
Swagger Generation Artifacts
|
PR validation pipeline started successfully. If there is ApiView generated, it will be updated in this comment. |
@rkmanda let's not add such large amount of text to the PR description: we were constantly running into the problem of having too much text which nobody reads, hence we are quite strict on the amount of text we are willing to put into a PR description. I will create a separate PR to do this update and offload most of this information into a dedicated aka.ms link in aka.ms/azsdkdocs. I will use this PR of yours for info what to write. Thx! |
Going forward, the PR assignee for each control plane PR will be left empty. This is an intentional change to streamline the collaboration between the PR author and the ARM reviewers. We now ask the authors to reserve an ARM office hours slot to discuss any questions they might have about their PR or if they need to get unblocked.
Relevant issue: