Open
Conversation
vanbroup
reviewed
Sep 5, 2024
docs/BR.md
Outdated
| @@ -2,6 +2,7 @@ | |||
| title: Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates | |||
| subtitle: Version 2.0.5 | |||
| author: | |||
Member
There was a problem hiding this comment.
The front matter is in YAML, not Markdown.
It should be linted as YAML where this nestling would not be expected.
Author
There was a problem hiding this comment.
I've removed the changes to the YAML frontmatter.
a6788f6 to
79a79c8
Compare
79a79c8 to
b27eb13
Compare
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
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 reason for this PR is the same that cabforum/forum#51, which is basically that Markdown lists should be surrounded by blank lines for correct presentation.
Additionally, you can see a concrete presentation problem example for the TLS BRs in cabforum/build-guidelines-action#51 (comment).
Finally, merging cabforum/build-guidelines-action#51 could prevent the introduction of this type of Markdown problems in the future.