Open mikekistler opened 1 year ago
Here's another instance: https://github.com/Azure/azure-rest-api-specs-pr/pull/11560
Another instance: https://github.com/Azure/azure-rest-api-specs-pr/pull/11517
This PR is failing the “Swagger Breaking Change” PR Check:
But the pipeline did not add the “BreakingChangesReviewRequired” label (maybe because the break is only to a preview api-version in the internal repo?).
The PR reviewer decided to add the label by hand:
About a week later the pipeline was retriggered and the bot removed the label:
In this particular case, a review is needed because the changes in the PR violate our Breaking Change policy – breaking changes are allowed when the break is to a prior preview and not a GA version, but only if the break is done in a new api-version, which was not the case here.
Related email thread for few people involved in the issue discussion:
Sent: Friday, March 17, 2023 8:00 AM
Subject: Breaking Changes labeling in the azure-rest-api-specs repo
The PR pipeline bot in azure-rest-api-specs-pr failed to add the "BreakingChangesReviewRequired" label to https://github.com/Azure/azure-rest-api-specs-pr/pull/11562 when this PR failed the "Breaking Change (Cross-Version)" PR check: