[Breaking Change] shows as Failed but Signoff API Spec Readiness shows as not required
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
New service working on the initial release of their beta SDKs for management plane. They have not published their initial preview API version. They are working on finalizing the changes to preview API version in the private repo and will publish at public preview launch.
The PR met API readiness for signoff, which looks to be correct as there is no ARM Review required for these changes and the breaking changes would not be relevant for this PR. However, it is confusing b/c the breaking change error and ARM review not available are seen earlier in the flow. The service team engineer pinged me b/c he was confused by these results.
- [ ] **Suggested requirement:** If ARM Review or Breaking Change are not relevant for the PR, then show not required on the earlier screens.
Contributor guide
Assessment
This issue has not been assessed yet.