Test runner looping over each data source and running tests #97
This file contains 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
name: Snyk Security | |
on: | |
pull_request: | |
branches: ["main"] | |
permissions: | |
contents: read | |
jobs: | |
snyk: | |
permissions: | |
contents: read # for actions/checkout to fetch code | |
security-events: write # for github/codeql-action/upload-sarif to upload SARIF results | |
actions: read # only required for a private repository by github/codeql-action/upload-sarif to get the Action run status | |
runs-on: ubuntu-latest | |
steps: | |
- uses: actions/checkout@v4 | |
- name: Set up Snyk CLI to check for security issues | |
# Snyk can be used to break the build when it detects security issues. | |
# In this case we want to upload the SAST issues to GitHub Code Scanning | |
uses: snyk/actions/setup@806182742461562b67788a64410098c9d9b96adb | |
# For Snyk Open Source you must first set up the development environment for your application's dependencies | |
# For example for Node | |
#- uses: actions/setup-node@v4 | |
# with: | |
# node-version: 20 | |
continue-on-error: true | |
env: | |
# This is where you will need to introduce the Snyk API token created with your Snyk account | |
SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }} | |
# Runs Snyk Code (SAST) analysis and uploads result into GitHub. | |
# Use || true to not fail the pipeline | |
- name: Snyk Code test | |
run: snyk code test --sarif > snyk-code.sarif || true |