chore(ci): Remove Semgrep GHA Workflow#1149
Closed
eduardoboronat-okta wants to merge 33 commits into
Closed
Conversation
Update Node.js version requirement in README
… of 'yarn publint'
…with pagination details
tanya732
previously approved these changes
Sep 11, 2025
Contributor
|
Closing this and manually create another PR |
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
5 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.
Semgrep is Okta's static application security testing tool. It was previously recommended to add Semgrep directly into CI/CD pipelines or workflows. However, the ProdSec team has enhanced the tooling, and Semgrep scanning is now built into the platform via a GitHub Application.
ℹ️ Details
Created by Sourcegraph batch change
eduardo.boronat/Remove-Semgrep-GHA-non-EMU.