Add documentation lint checks to CI/CD testing

This issue has been tracked since 2022-09-20.

Describe the problem that you experienced

Currently documentation linting is available for use on a voluntary basis.

To improve newly submitted content, the lint testing should be part of the CI/CD testing so that all new documentation and documentation updates must past the documentation lint evaluation before they can be merged.

Enter the URL of the topic with the problem

N/A

Describe what you were looking for in the documentation

Looking at recent documentation contributions: many had lint errors, but because the lint testing isn't mandatory, they have been able to be merged with those errors.

Describe the actions that led you to experience the problem

While reviewing new documentation contributions.

Describe what you want to experience that would fix the problem

New documentation contributions and edit should have no lint errors.

Add a screenshot if that helps illustrate the problem

N/A

If this problem caused an exception or error, please paste it here

N/A

If the problem is browser-specific, please specify the device, OS, browser, and version

N/A

Provide any additional information here in as much as detail as you can

For information about the linter, see:
* https://angular.io/guide/docs-lint-errors
* https://github.com/angular/angular/tree/main/aio/tools/doc-linter#angular-documentation-lint-tool
* https://vale.sh/
More Details About Repo
Owner Name angular
Repo Name angular
Full Name angular/angular
Language TypeScript
Created Date 2014-09-18
Updated Date 2022-09-30
Star Count 84091
Watcher Count 3064
Fork Count 22233
Issue Count 1203

YOU MAY BE INTERESTED

Issue Title Created Date Updated Date