Conversation
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
❗ By default, the pull request is configured to backport to all release branches.
|
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
3 similar comments
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
e25b1a3 to
d160cef
Compare
|
/ok-to-merge snyk workflow improvement |
d160cef to
d6580bb
Compare
Until now we were running only the `test` command from the snyk CLI, but there's another command we should be using `code test` for static analysis. Closes #6058 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
d6580bb to
bef6414
Compare
Until now we were running only the
testcommand from the snyk CLI, but there's another command we should be usingcode testfor static analysis.Closes #6058