Skip to content

superlinter updated #37

superlinter updated

superlinter updated #37

Workflow file for this run

name: "CodeQL"
on:
push:
# Run CodeQL on pushes to main (adapt if your default branch is different)
branches: [ "main" ]
pull_request:
# Analyze pull requests targeting main
branches: [ "main" ]
# Allow manual runs from the GitHub Actions UI
workflow_dispatch:
jobs:
analyze:
name: Analyze (CodeQL)
runs-on: ubuntu-latest
# We explicitly tell CodeQL which languages to analyze.
# For Trice, we have:
# - Go code -> language: "go"
# - C sources/headers -> language: "cpp" (covers C/C++)
strategy:
fail-fast: false
matrix:
language: [ "go", "cpp" ]
steps:
# Checkout the repository so CodeQL can see the source code.
- name: Checkout repository
uses: actions/checkout@v4
# Initialize the CodeQL tools for the selected language.
- name: Initialize CodeQL
uses: github/codeql-action/init@v3
with:
# Use the current matrix language (go or cpp).
languages: ${{ matrix.language }}
# Optional: specify custom queries or query packs here if needed.
# queries: security-and-quality
# Autobuild step:
# - For "go", CodeQL does not strictly need a traditional build; it can
# analyze the source directly.
# - For "cpp", CodeQL tries to automatically build the project to
# understand the compiled artifacts (C/C++ code).
#
# If autobuild fails for your C parts, you may need to:
# - remove this step, and
# - add a manual build step (e.g. make, cmake, etc.).
- name: Autobuild
uses: github/codeql-action/autobuild@v3
# Perform the actual CodeQL analysis and upload the results to GitHub.
# Results show up under the "Security" -> "Code scanning alerts" tab.
- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v3