cpp-linter-action v2.9.0 Introduces Pull Request Review Capability
The cpp-linter-action tool, a GitHub Action for C/C++ linting, has been updated to version 2.9.0 adding a Pull Request Review feature that posts suggestions directly in PRs, along with other functionalities such as Annotations, Thread Comments, and Step Summaries.
As the creator and contributor of cpp-linter , I am pleased to announce that starting from version v2.9.0 , cpp-linter-action supports the Pull Request Review feature.
Below are the release notes for cpp-linter-action. The most important change is the bump of cpp-linter from 1.6.5 to 1.7.1 (see #191). Note that the cpp-linter package is the core dependency of cpp-linter-action.
What is cpp-linter-action
If you are not familiar with cpp-linter-action, you can refer to my previous article (link). In short, cpp-linter-action is a GitHub Action under the cpp-linter organization that formats C/C++ code, provides diagnostics, and automatically fixes typical programming errors.
Currently, cpp-linter-action is used by more than 500 open‑source projects (closed‑source usage is not counted), including well‑known organizations such as Microsoft, the Linux Foundation, CachyOS, Nextcloud, and Jupyter.
It can be considered the best linter choice for C/C++ projects on GitHub.
About the Pull Request Review Feature
The newly added Pull Request Review feature can automatically post review suggestions after cpp-linter-action finishes its checks. Developers no longer need to apply fixes locally; they can simply click the Commit suggestions button on GitHub to merge the suggested changes directly into the current pull request, eliminating manual edits and pushes.
Once all suggestions are resolved, the GitHub‑action bot automatically approves the pull request.
Other Supported Features of cpp-linter-action
In addition to Pull Request Review, cpp-linter-action also supports three other options: Annotations, Thread Comment, and Step Summary.
GitHub Annotations
Shows execution results as inline annotations at the relevant lines of code.
Thread Comment
Posts execution results as comments on the pull request.
Step Summary
Displays execution results in the GitHub Action job summary view.
The Story Behind This Release
I finally found time on the night of the eighth day of the Lunar New Year to write this article and record the story behind the release.
I would like to thank the co‑creator of cpp-linter, @2bndy5 , whose contributions were essential. Although we have never met in person, we have collaborated for three years through GitHub issues and pull requests, communicating privately via email when needed.
Recently, @2bndy5 faced personal difficulties and took a break from coding, but he continued to test the Pull Request Review feature, update documentation, and prepare the release while I dealt with a series of family health issues.
Despite these challenges, the work on the new feature was completed, and I was eager to review and test the contributions when I returned to work.
Finally, you are welcome to use any project under the cpp-linter organization and provide your valuable feedback, suggestions, or code contributions.
— Published on 2024‑02‑17 23:34
References
[1] cpp-linter:
https://github.com/cpp-linter
[2] release notes:
https://github.com/cpp-linter/cpp-linter-action/releases
[3] #191:
https://github.com/cpp-linter/cpp-linter-action/pull/191
[4] cpp-linter-action:
https://github.com/cpp-linter/cpp-linter-action
[5] Previous article:
https://shenxianpeng.github.io/2022/08/cpp-linter/
[6] GitHub Action:
https://docs.github.com/en/actions/quickstart
[7] @2bndy5:
https://github.com/2bndy5
DevOps Engineer
DevOps engineer, Pythonista and FOSS contributor. Created cpp-linter, commit-check, etc.; contributed to PyPA.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.