[LintDiff] Report generator shows when "before" state has errors #36126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #36082
Example PR with swagger changes and autorest failing in the
beforestate. In this case the table notes "Autorest failed" and there's a warning. Since there are no prior violations to compare (because of the autorest failure) all violations in theafterstate are treated as "new":https://github.com/Azure/azure-rest-api-specs/actions/runs/16475273232
Example PR with fixes to
readme.md. In this case, the PR did not change any swagger files. LintDiff only surfaces errors for affected swaggers which, when no swagger files are edited, is an empty set.https://github.com/Azure/azure-rest-api-specs/actions/runs/16475290346?pr=36137