Add static analysis using fortitude, clang, and ruff #1
Workflow file for this run
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
# workflow to run static-analysis and linting checks on C/C++ files | ||
name: C/C++Lint | ||
# Controls when the workflow will run | ||
on: | ||
# Triggers the workflow on pushes to the "main" branch and any pull request events | ||
push: | ||
branches: [ "main"] | ||
pull_request: | ||
# Allows you to run this workflow manually from the Actions tab | ||
workflow_dispatch: | ||
# Workflow run - one or more jobs that can run sequentially or in parallel | ||
jobs: | ||
# This workflow contains a single job called "test-suite" | ||
C-C++-lint: | ||
Check failure on line 18 in .github/workflows/cpp-linter.yml GitHub Actions / C/C++LintInvalid workflow file
|
||
# The type of runner that the job will run on | ||
runs-on: ubuntu-latest | ||
strategy: | ||
fail-fast: false | ||
# Steps represent a sequence of tasks that will be executed as part of the job | ||
steps: | ||
- uses: actions/checkout@v4 | ||
- uses: cpp-linter/cpp-linter-action@v2 | ||
id: linter | ||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
with: | ||
style: 'file' # Use .clang-format config file | ||
tidy-checks: '' # Use .clang-tidy config file | ||
# only 'update' a single comment in a pull request thread. | ||
thread-comments: ${{ github.event_name == 'pull_request' && 'update' }} | ||
- name: Fail fast?! | ||
if: steps.linter.outputs.checks-failed > 0 | ||
run: exit 1 |