Azure / Azure/azure-rest-api-specs

[EngSys] ModelValidation, SemanticValidation, and BreakingChanges should ignore common-types

Open
#33,056 0 comments 0 reactions 1 assignee Claimed by @mikeharder View on GitHub
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

PR: https://github.com/Azure/azure-rest-api-specs/pull/33043

Checks ModelValidation, SemanticValidation, and BreakingChanges are all failing, because they consider the changes to `specification/common-types` as "spec changes" and try to validate the files, which always fails since they're aren't complete specs.

Fix is to exclude `/specification/common-types/**` and `/*.json` (json files in repo root) when detecting spec files to analyze.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.