Swagger lintdiff showing green even when there are underlying failures
- Dominant language
- TypeSpec
- Stars
- 4.8k
- Forks
- 736
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 1
Description
**Before filling a bug**
- [ X] have you checked the [faq](https://github.com/Azure/autorest/tree/main/docs/faq.md) for known issues.
- [ X] have you checked existing issues
Swagger lintdiff encountered a failure but shows up as healthy
PR link: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3225367&view=logs&j=0574a2a6-2d0a-5ec6-40e4-4c6e2f70bea2&t=80c3e782-49f0-5d1c-70dd-cbee57bdd0c7
```
Please provide as much information as you can. This would be:
- OpenAPI files having the issues
- Autorest command used
```
**Expected behavior**
When errors are encountered the automated check must fail
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start by reviewing the linked Azure DevOps build logs for the Swagger lintdiff failure and trace how that failure is reported to the automated check. Done means a lintdiff error causes the check to fail instead of showing a healthy result; the issue does not name repository files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100