Fix MD027 violation on sql-server.md #892
Merged
Conversation
This file contains 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
markdownlint was complaining because there was a blockquote defined without an angle bracket on each line. This triggered <https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md027---multiple-spaces-after-blockquote-symbol>. I think what's happened is that the docs folder wasn't configured to trigger an Azure Pipelines build, so the check was never run on the PR. I've updated the pipelines file to trigger a build on changes to the docs folder now.
|
Good point, I'll open an issue for it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
markdownlint was complaining because there was a blockquote defined without an angle bracket on each line. This triggered https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md027---multiple-spaces-after-blockquote-symbol.
I think what's happened is that the docs folder wasn't configured to trigger an Azure Pipelines build, so the check was never run on the PR. I've updated the pipelines file to trigger a build on changes to the docs folder now.
@tomkerkhove do you think it makes sense to have a separate pipeline for the docs folder so it doesn't need to run a full build of the code if you're just making a documentation change? I went with the easy option of just adding the docs folder for now, but I figured it was worth asking.