doc: fix markdown linter for release changelogs #47
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
santigimeno
reviewed
Dec 13, 2023
santigimeno
requested changes
Jan 26, 2024
Signed-off-by: Juan José Arboleda <soyjuanarbol@gmail.com>
juanarbol
force-pushed
the
juan/fix-md-linter
branch
from
73057bc
to
7a67284
Compare
santigimeno
approved these changes
Jan 29, 2024
juanarbol
added a commit
that referenced
this pull request
Feb 12, 2024
Signed-off-by: Juan José Arboleda <soyjuanarbol@gmail.com> PR-URL: #47 Reviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>
trevnorris
pushed a commit
that referenced
this pull request
Feb 28, 2024
Signed-off-by: Juan José Arboleda <soyjuanarbol@gmail.com> PR-URL: #47 Reviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>
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.
This, besides fixing the md linter (add
<!--lint disable maximum-line-length no-literal-urls prohibited-strings-->as Node.js does), proposes following the changelog file structure adopted by Node.js core, it separates each release line instead of having a single changelog file for all release lines.