Open gone-for-coding opened 1 year ago
I can confirm it is reproduced on Mac OS, too.
It is still an issue; MacOS Sonoma, latest vs code
I fixed it by adding the following in my settings.yml of vscode
"yaml.customTags": [
"!reference sequence"
],
I have added the configuration suggested by @gjrtimmer but still getting an error 😢
{
"yaml.customTags": ["!reference sequence"]
}
I have added the configuration suggested by @gjrtimmer but still getting an error 😢
{ "yaml.customTags": ["!reference sequence"] }
I think this is actually an issue with the schema which GitLab publishes. I just encountered that same error for a services
block as well as the rules
block you referenced, but they do work for before_script
and script
so I opened a GitLab issue about the schema after confirming that validation passes if I add {"$ref":"#/definitions/!reference"}
to the list of allowed values for that schema:
Describe the bug
Expected Behavior
This code is actually valid:
.gitlab-ci.yml
The correct schema is loaded: https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catalog.json#L1732 https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/editor/schema/ci.json#L29
Current Behavior
Problems are raised for each !reference tag in the file: Unresolved tag: !reference
Steps to Reproduce
Use the above mentioned file.
Environment