Josh Pinkney

Did you fork the repository before you cloned it? It looks like you're trying to push directly to upstream

To test your changes with VSCode you can follow these steps: https://github.com/redhat-developer/vscode-yaml/blob/master/CONTRIBUTING.md#developing-the-client-and-server-together Let me know if you have any issues with those and I can help further!

We have a fix for: > unable to get local issuer certificate coming in the next few days (when 0.14.0 is released) and that should fix your issue I believe....

We've just release vscode-yaml 0.14.0 and it should be available on the marketplace. When you get a chance can you try again and let me know what the result is

For a workaround if you can access https://json.schemastore.org/ansible-playbook you can download it and then reference it locally in yaml.schemas. So you can do something like: ``` "yaml.schemas": { "./schemas/ansible-playbook.yml": ["*.yml"]...

This all depends on [prettier](https://github.com/prettier/prettier) adding this configuration or seeing if they have some api that allows to change array configuration.

I can actually reproduce this on my end. It looks like the glob pattern from the schema store isn't working. I can also reproduce this without the schema store by...

Just tested this out on 0.18.0 and can reproduce. Adding the bug label

Those issues don't seem to be related. Please file a new issue for that

Which version of vscode-yaml are you using? If you set the `yaml.trace.server` setting to `verbose` in the vscode settings and then go to the `YAML support` output channel is there...