docs: extended security guide to include OpenSSF tooling #5217
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
ovflowd
approved these changes
Mar 31, 2023
|
Hey team, can we |
RafaelGSS
approved these changes
Mar 31, 2023
aymen94
approved these changes
Mar 31, 2023
SEWeiTung
reviewed
Mar 31, 2023
SEWeiTung
approved these changes
Mar 31, 2023
shanpriyan
reviewed
Apr 1, 2023
|
We need one more sign-off from @nodejs/security |
Co-authored-by: Shanmughapriyan S <[email protected]> Signed-off-by: Claudio Wunder <[email protected]>
manishprivet
approved these changes
Apr 1, 2023
That's fine. I think we can land 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.
Hi all!
I am not very sure about how to manage the translations with the latests changes, but I am happy to update the spanish version for this change as well in this PR or in a separate one.
Regarding the pure content changes, let's see if there are at least 2 more members of the @nodejs/security that can review it before we merge it. 😉
We discuss to include this references in nodejs/security-wg#932