-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Software Supply Chain Best Practices v2 markdown #1396
Conversation
✅ Deploy Preview for tag-security ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@mnm678 To what extent do you want to resolve the linter findings before merging this? No hard opinions here - might be a few spelling items worth review. |
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Authors: Original White Paper authors, Marina Moore, Michael Lieberman, John Kjell, James Carnegie, Ben Cotton | ||
Reviewers: | ||
|
||
# Scope: {#scope:} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like GitHub auto-generates this heading ids: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#section-links.
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
The remaining link error is a link to the file added in this pr, which should work once this is merged. And the remaining linter errors are for duplicate headings, which I disagree with (I actually think it's more clear to have a consistent document structure). Which means this is ready for review! |
I made this PR for the linter config which should resolve those. I agree that this should be allowed. #1397 |
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor callouts - feel free to consider these against the source-of-truth and otherwise resolve.
I will follow-up with resolving these comments to approve if helpful.
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Brandt Keller <[email protected]> Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
Thanks @brandtkeller! Feedback applied |
community/working-groups/supply-chain-security/suply-chain-security-paper-v2/SSCBPv2.md
Outdated
Show resolved
Hide resolved
…urity-paper-v2/SSCBPv2.md Co-authored-by: Brandt Keller <[email protected]> Signed-off-by: Marina Moore <[email protected]>
Signed-off-by: Marina Moore <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Content looks great - all of my concerns were resolved.
The Software Supply Chain working group has been working on an update to the Software Supply Chain Best Practices Paper. This is the markdown version of the document we have been working on.