feat: codeql workflow for ts and rust - #1864
Conversation
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
|
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. |
There was a problem hiding this comment.
Pull request overview
This PR implements a comprehensive security scanning workflow to replace the GitHub CodeQL extension, which doesn't support fork PRs. The workflow adds CodeQL analysis for TypeScript/JavaScript and Rust, plus additional security scanning for Dockerfiles and shell scripts, with weekly automated scans on the main branch.
Key Changes:
- CodeQL security analysis for JavaScript/TypeScript and Rust with extended security queries
- Hadolint scanning for Dockerfile security and best practices
- ShellCheck integration for shell script linting
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
ravinagill15
left a comment
There was a problem hiding this comment.
Looks good, just minor comments / clarifications
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
3a46b0f to
0312338
Compare
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
a81c644 to
d48ad27
Compare
🚨 E2E Tests FailedThe E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:
This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information. |
|
|
||
| # Cancel in-progress runs when a new commit is pushed | ||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} |
There was a problem hiding this comment.
I think this will only cancel in-progress runs in a same PR.
I'm guessing it's ok.
There was a problem hiding this comment.
yeah thats what we wanna do
CodeQL extension does not run on fork prs into devtools. This workflow yaml should effectively replace the extension.
Also took the liberty to add in:
DockerfilescanningShell scriptscanningontop of
codeql'sjs-tsandrustIt also runs weekly scans on
main