[PR Workflow] Add a linter rule to flag json parsing issues. Do not add the WaitForARMFeedback label until the author resolves the issue
Open
Central-EngSys
feature-request
Spec PR Tools
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
If the open API spec is not well-formed JSON, none of the other automated checks would be able to run and there is no use of performing a review for PRs in this state. We would first like the author to fix the basic issues before proceeding with the review. The `WaitForARMFeedback` label can then be added later by the bot once the json parsing issue is addressed.
Contributor guide
Assessment
This issue has not been assessed yet.