Skip to content

doc: make YAML matter consistent in crypto.md - #30016

Merged
Trott merged 1 commit into
nodejs:masterfrom
Trott:fix-yaml-processing
Oct 18, 2019
Merged

doc: make YAML matter consistent in crypto.md#30016
Trott merged 1 commit into
nodejs:masterfrom
Trott:fix-yaml-processing

Conversation

@Trott

Copy link
Copy Markdown
Member

This fixes YAML that gets incorrectly processed by our tooling.

Refs: #29910 (comment)

@vsemozhetbyt

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added crypto Issues and PRs related to the crypto subsystem. doc Issues and PRs related to the documentations. labels Oct 18, 2019
@Trott

Copy link
Copy Markdown
MemberAuthor

Collaborators, please 👍 here to fast-track.

@TrottTrott added the fast-track PRs that do not need to wait for 48 hours to land. label Oct 18, 2019
@Trott

Copy link
Copy Markdown
MemberAuthor

@TrottTrott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Oct 18, 2019
@richardlau

Copy link
Copy Markdown
Member

We should (in another PR) make the tooling throw some sort of error on the original YAML rather than silently incorrectly process it and rely on a human eyeballing the generated docs.

This fixes YAML that gets incorrectly processed by our tooling.
Refs: nodejs#29910 (comment)
PR-URL: nodejs#30016
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@Trott
Trottforce-pushed the fix-yaml-processing branch from fdfc434 to ce72cd7CompareOctober 18, 2019 16:11
@Trott

Copy link
Copy Markdown
MemberAuthor

Landed in ce72cd7

@Trott
Trott merged commit ce72cd7 into nodejs:masterOct 18, 2019
MylesBorins pushed a commit that referenced this pull request Oct 23, 2019
This fixes YAML that gets incorrectly processed by our tooling.
Refs: #29910 (comment)
PR-URL: #30016
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@targostargos mentioned this pull request Nov 5, 2019
@targos

Copy link
Copy Markdown
Member

Depends on #29910 to land on v12.x

targos pushed a commit that referenced this pull request Jan 8, 2020
This fixes YAML that gets incorrectly processed by our tooling.
Refs: #29910 (comment)
PR-URL: #30016
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
targos pushed a commit that referenced this pull request Jan 8, 2020
This fixes YAML that gets incorrectly processed by our tooling.
Refs: #29910 (comment)
PR-URL: #30016
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@targostargos mentioned this pull request Jan 15, 2020
BethGriggs pushed a commit that referenced this pull request Feb 6, 2020
This fixes YAML that gets incorrectly processed by our tooling.
Refs: #29910 (comment)
PR-URL: #30016
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@MylesBorinsMylesBorins mentioned this pull request Feb 8, 2020
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.cryptoIssues and PRs related to the crypto subsystem.docIssues and PRs related to the documentations.fast-trackPRs that do not need to wait for 48 hours to land.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Trott@richardlau@targos@jasnell@cjihrig@gireeshpunathil@nodejs-github-bot