Skip to content
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 electron as a source (xs sized PR) #1921

Conversation

s-santillan
Copy link
Collaborator

@s-santillan s-santillan commented Jan 23, 2025

Thanks for improving Semgrep Docs 😀

Please ensure

  • A subject matter expert (SME) reviews the content
  • A technical writer reviews the content or PR

Tiny PR. I checked our Advisories tab and we don't show the source of the CVE (yet) so I just listed electron release notes as a source.

Copy link

netlify bot commented Jan 23, 2025

Don't forget to add /docs at the end of the deploy preview site URL!

Name Link
🔨 Latest commit be9a0c7
🔍 Latest deploy log https://app.netlify.com/sites/semgrep-docs-prod/deploys/6791ee4f7fd1dd00082c0dfd
😎 Deploy Preview https://deploy-preview-1921--semgrep-docs-prod.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Collaborator

@khorne3 khorne3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should update the header on the Supported Languages table where it says, "Period of reachability rule coverage for CVEs/GHSAs" too?

@s-santillan
Copy link
Collaborator Author

@khorne3 I thought about it - my first pass was "Period of reachability rule coverage for advisory sources" which sounded pretty weird. (We're going to have a third rule source within 1-2 months so I had to generalize to "security advisory sources" or some such.) Also there was no mention of "time period coverage" during the product-updates announcement so I'm not sure we go back to 201X for Electron specifically.

@khorne3
Copy link
Collaborator

khorne3 commented Jan 23, 2025

@s-santillan That makes sense. If/when we need to make these updates, maybe we just shorten the header to "Period of reachability rule coverage" and make sure the text is descriptive enough to be clear

@s-santillan s-santillan merged commit 8e82f28 into main Jan 25, 2025
7 checks passed
@s-santillan s-santillan deleted the sara/tec-267-docs-update-we-now-integrate-electron-release-notes-for branch January 25, 2025 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants