docs: fix MD019 double space in Grafana MCP guide heading#25137
Merged
craig-osterhout merged 1 commit intoMay 21, 2026
Conversation
The 'Data source Discovery' heading had two spaces after the ###, which fails the markdownlint check (MD019) for the whole content tree.
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
2 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.
The "Data source Discovery" heading in
content/guides/grafana-mcp-server-gemini.mdhas two spaces after the###, which trips markdownlint (MD019). Since the lint job runs over the wholecontent/**/*.mdtree, this currently fails CI on every open PR. This removes the extra space.