vscode-yaml: .gitlab-ci.yml validation errors

Not sure this is correct?

.gitlab-ci.yml is the correct file name, it is the linter that only works if you rename it to yaml

It appears to, yes

Can we get an update to such a simple problem?

The extensions page says it uses schema store to automatically try to match up the schema using the file name you’re editing.

Having a look at the gitlab-ci schema on the schema store here it seems like this just doesn’t match up with the actual schema gitlab expects.

Changing the file to .yaml makes this lookup not match/not happen.

You can change these settings in vscode in your settings.json:

"yaml.schemas": {
    "http://json.schemastore.org/composer": ["/*"],
    "file:///home/johnd/some-schema.json": ["some.yaml"],
    "../relative/path/schema.json": ["/config*.yaml"],
    "/Users/johnd/some-schema.json": ["some.yaml"],
}

There are some open issues on gitlab for them to host their own json schema for gitlab-ci files. Basically what’s out there just gets outdated and gitlab has to make pull requests if they change the schema and the whole thing might just be too slow.

Sorry if that’s not very helpful but that’s about all I could come up with trying to solve the issue.

If you had a valid schema file for the gitlab-ci file (which maybe you could find in a PR over at the json store repo) you could put something in like:

    "file:///home/johnd/gitlab-schema.json": [".gitlab-ci.yml"],

But I can’t find a better schema file myself.