Hello, I'd like to ask what the motivation is for this fork. I assume it's to support some features that Azure Pipelines uses that aren't standard YAML/JSON? Or to customize the performance/parsing in other ways?

Are there any plans to sync this fork with the Red Hat upstream repo? It looks like the last commit from upstream was in 2018. Since then there have been numerous improvements/bugfixes that are not reflected on this fork. Likewise, there are improvements/bugfixes on this fork that are not reflected upstream.

I'm a user of LSP, but I don't consume the language server from VSCode, so this situation was a bit confusing for me when I tried to use the normal yaml-language-server to parse Azure Pipelines yaml. Even now that I'm aware of this fork, it's very difficult to configure my editor to use your language server for certain files and the upstream language server for others.

If a major purpose of this fork is to implement non-standard JSON/YAML features, have you considered trying to make those features standard? One non-standard feature that I've noticed is Azure Pipeline's use of aliases, and there's discussion over on json-schema-org about making that part of the spec. Perhaps one of the maintainers of this fork could weigh in on that conversation?

Thank you in advance for any clarification you can provide.