Chris Stackhouse
Chris Stackhouse
@prchalla1 - I don't see a response to this comment: https://github.com/Azure/azure-rest-api-specs/pull/21560#discussion_r1051236626. This is important: please let us know. I'll summarize the issue here: Currently you are using a singleton "default"...
> @jayati-tehri, @prchalla1 - This is one reason it is critical that new API PRs follow this format: **Adding a new API version -[ ] To review changes efficiently, ensure...
> @mentat9 Hi Chris, > > The reason we didn’t copy the previous folder into the new version 2022-06-01 is because we are introducing 2022-06-01 only for pricesheets and operations...
@paterasMSFT - This PR is marked for ARM review but is draft and hasn't had activity for quite a while. If/when you are ready for ARM review, set it Open....
@thatChang - Couple of things: 1. This PR has been off of ARM review's radar because you didn't remove the ARMChangesRequested label (comment here; https://github.com/Azure/azure-rest-api-specs/pull/20803#issuecomment-1273856308). Please remove the label in...
@thatChang - I didn't see any response to my comments: https://github.com/Azure/azure-rest-api-specs/pull/20803#issuecomment-1370277643. Note, at minimum before your new API can be reviewed by ARM you will need to provide a PR...
> @mentat9 I have a new PR #22077 with the base required. For the reason why the old versions were edited. It's because S360 reports issues from multiple versions, including...
@thatChang - Please close this PR if it's no longer needed.
@brpanask - Please fix the checks, set your PR to Open, and apply the WaitForARMFeedback label if/when you are ready for ARM review. If you no longer need this PR,...