Codecov Report

❗ No coverage uploaded for pull request base (main@eb81b8f). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   80.75%           
=======================================
  Files           ?        6           
  Lines           ?      639           
  Branches        ?        0           
=======================================
  Hits            ?      516           
  Misses          ?      123           
  Partials        ?        0           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Ok I replaced most of the references to the old cpp-linter-action origin. I just want to point out that there are still a few that shouldn't be changed (or don't need to be changed):

1. This is a hyperlink in the README to the cpp-linter-action which should contain how to use the pkg in a YAML file. I think the cpp-linter-action/README doesn't need to change after switching to composite action. But the README here should really focus on the executable script's CLI args.
   • Sphinx can be used to get the cpp-linter -h output and create a document from that, so the README here might just forward to the docs in the future. PyPi doesn't use Sphinx to parse the README, so it would throw an error if we generate this doc about CLI args in the README (must be done on a separate page).
2. This test is using a specific commit from the test-cpp-linter-action repo. So, this doesn't need to change because the git history won't change there. After we get the migration complete (using the composite action approach), we can change the test here, but it isn't mandatory.

The blurry logo in this PR should also be updated

I've already updated the logo locally for this repo. But I'm working on updating the cpp-linter -h output, so we can use it to generate a cross-referencable doc.

I created a gh-pages branch and uploaded the last local build of the docs. They are now live at https://cpp-linter.github.io/cpp-linter

The CLI args are now automatically documented on a separate page (which the README now links to) -- see https://cpp-linter.github.io/cpp-linter/cli_args.html This means we no longer have to update 2 copies of the descriptions for the CLI args. The descriptions are now fetched from cpp-linter -h output.

Merging this and releasing it to PyPI will be a big step towards switching to a composite action.