Skip to content

Validate submodel reference in JSON Schema #280

Validate submodel reference in JSON Schema

Validate submodel reference in JSON Schema #280

Triggered via pull request December 12, 2023 14:56
Status Failure
Total duration 24s
Artifacts
Check-title-and-description-of-pull-request
11s
Check-title-and-description-of-pull-request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Check-title-and-description-of-pull-request
The message 1 is invalid: * The subject must start with a verb in imperative mood, but it started with: "Validate". Whether the word is in imperative mood is determined by whitelisting. The general whitelist is available at https://github.com/mristin/opinionated-commit-message/blob/master/src/mostFrequentEnglishVerbs.ts. You can whitelist additional verbs using "additional-verbs" input to your GitHub action (currently no additional verbs were thus specified). Moreover, you can also whitelist additional verbs in a file given as "path-to-additional-verbs" input to your GitHub action (currently the file is: .github/workflows/AdditionalVerbsInImperativeMood.txt). Please check the whitelist and either change the first word of the subject or whitelist the verb. * The line 3 of the message (line 1 of the body) exceeds the limit of 72 characters. The line contains 148 characters: "This will propose more restriction which validate the submodel references in AssetAdministrationShell to be only `ModelReference<SubmodelReference>`". Please reformat the body so that all the lines fit 72 characters. The original message was: Validate submodel reference in JSON Schema This will propose more restriction which validate the submodel references in AssetAdministrationShell to be only `ModelReference<SubmodelReference>`
Check-title-and-description-of-pull-request
The following actions uses node12 which is deprecated and will be forced to run on node16: mristin/opinionated-commit-message@v3.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/