doc: add nodejs/tweet issue creation to sec. doc#39940
Closed
danbev wants to merge 1 commit intonodejs:masterfrom
Closed
doc: add nodejs/tweet issue creation to sec. doc#39940danbev wants to merge 1 commit intonodejs:masterfrom
danbev wants to merge 1 commit intonodejs:masterfrom
Conversation
This commit adds a suggestion to create a github issue for the security release tweets. Currently, the security release document requests that these tweets be created by asking in the #nodejs-social channel. Someone from that channel would then create an issue, so we could just create the issue ourselves.
jasnell
approved these changes
Aug 30, 2021
cjihrig
approved these changes
Aug 30, 2021
danbev
added a commit
that referenced
this pull request
Sep 1, 2021
This commit adds a suggestion to create a github issue for the security release tweets. Currently, the security release document requests that these tweets be created by asking in the #nodejs-social channel. Someone from that channel would then create an issue, so we could just create the issue ourselves. PR-URL: #39940 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Contributor
Author
|
Landed in 5b2ab7a |
targos
pushed a commit
that referenced
this pull request
Sep 6, 2021
This commit adds a suggestion to create a github issue for the security release tweets. Currently, the security release document requests that these tweets be created by asking in the #nodejs-social channel. Someone from that channel would then create an issue, so we could just create the issue ourselves. PR-URL: #39940 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
targos
pushed a commit
that referenced
this pull request
Sep 6, 2021
This commit adds a suggestion to create a github issue for the security release tweets. Currently, the security release document requests that these tweets be created by asking in the #nodejs-social channel. Someone from that channel would then create an issue, so we could just create the issue ourselves. PR-URL: #39940 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
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
4 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.
This commit adds a suggestion to create a github issue for the security
release tweets. Currently, the security release document requests that
these tweets be created by asking in the #nodejs-social channel. Someone
from that channel would then create an issue, so we could just create
the issue ourselves.