Repository files navigation

Each time new code is pushed into your repo, you can have acpplint command automatically run.

Example workflow:

• Put the following text into a file named.github/workflows/cpplint.yml in your repo):

name:cpplinton:[push, pull_request]jobs:cpplint:runs-on:ubuntu-lateststeps:    -uses:actions/checkout@v4    -run:pipx run cpplint --recursive .

Customize the final line to match your requirements.

Syntax: cpplint.py [--verbose=#] [--output=emacs|eclipse|vs7|junit]                   [--filter=-x,+y,...]                   [--counting=total|toplevel|detailed] [--repository=path]                   [--root=subdir] [--linelength=digits] [--recursive]                   [--exclude=path]                   [--headers=ext1,ext2]                   [--extensions=hpp,cpp,...]        <file> [file] ...

cpplint_modified_files.yml is analternative, standalone GitHub Action that enables a repo to achievegradual compliance with cpplint by linting (and compiling) only those files that have been added or modified (vs. origin/master).

1. runs cpplint only on those files that have been modified vs. origin/master.
2. compiles with g++ only those files that have been modified vs. origin/master.
3. other optional filepath verifications may be commented out at the end of this file.