Conversation
In VSCode or any of its forks with the [YAML](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) extension installed, adding the schema URL at the start of the file enables linting
ilbertt
commented
Nov 3, 2025
ilbertt
commented
Nov 3, 2025
lwshang
approved these changes
Nov 3, 2025
Contributor
Author
|
Let's wait for the first release to come out, so that we can pin the URL of the schema to it. For this reason, I'm converting this to draft for now. |
ilbertt
commented
Nov 10, 2025
raymondk
approved these changes
Nov 25, 2025
Contributor
Author
|
Now that the first beta is out, we can merge this and update it to the first stable as soon as it's available. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In VSCode or any of its forks with the YAML extension installed, adding the schema URL at the start of the file enables linting.
After we publish the docs on a static URL, we should use that URL instead of the raw GitHub file URL.