Skip to content

Add metadata fields for mappings (content gap initiative) #9665

Add metadata fields for mappings (content gap initiative)

Add metadata fields for mappings (content gap initiative) #9665

Triggered via pull request July 17, 2024 18:39
Status Success
Total duration 1m 22s
Artifacts

vale.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
[vale] _field-types/index.md#L143: _field-types/index.md#L143
[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'true,false'.
[vale] _field-types/metadata-fields/index.md#L2: _field-types/metadata-fields/index.md#L2
[OpenSearch.HeadingColon] Capitalize the word after a colon in ': default'.
[vale] _field-types/metadata-fields/index.md#L5: _field-types/metadata-fields/index.md#L5
[OpenSearch.HeadingColon] Capitalize the word after a colon in ': true'.
[vale] _field-types/metadata-fields/index.md#L6: _field-types/metadata-fields/index.md#L6
[OpenSearch.HeadingColon] Capitalize the word after a colon in ': false'.
[vale] _field-types/metadata-fields/source.md#L11: _field-types/metadata-fields/source.md#L11
[OpenSearch.Spelling] Error: fethc. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
style-job
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/