# cpp-linter > clang-format and clang-tidy for C and C++, in pull requests, pre-commit hooks and CI. ## Pages - [Home](https://cpp-linter.github.io/index.md): clang-format and clang-tidy for C and C++ pull requests, pre-commit hooks and CI, with the LLVM version you pin. - [Get started](https://cpp-linter.github.io/getting-started.md): Set up cpp-linter-action, the cpp-linter pre-commit hooks, the cpp-linter command or the clang tools, with the LLVM version you pin. - [Other CI](https://cpp-linter.github.io/other-ci.md): Run clang-format and clang-tidy on the files a branch changes in GitLab CI, Jenkins, Azure Pipelines and Bitbucket Pipelines, with the cpp-linter command. - [AI coding agents](https://cpp-linter.github.io/ai-coding-agents.md): Make clang-format and clang-tidy the check an AI coding agent runs after it edits C or C++ code, with configs for Claude Code, GitHub Copilot coding agent, AGENTS.md, pre-commit and pull requests. - [Why cpp-linter](https://cpp-linter.github.io/why-cpp-linter.md): How cpp-linter compares with other clang-format and clang-tidy GitHub Actions and pre-commit hooks, and how to migrate. - [Showcase](https://cpp-linter.github.io/showcase.md): Open-source projects that run cpp-linter-action, ranked by GitHub stars, and some that use cpp-linter-hooks. - [Community](https://cpp-linter.github.io/discussion.md): Where to ask about cpp-linter, report bugs and security problems, and contribute. - [Sponsor](https://cpp-linter.github.io/sponsor.md): Sponsor cpp-linter through GitHub Sponsors or Open Collective. Sponsor tiers include your logo on the website and READMEs and thanks in release notes. ## Blog - [Blog](https://cpp-linter.github.io/blog/index.md): Guides to running clang-format and clang-tidy with cpp-linter. ## Blog / Archive - [2026](https://cpp-linter.github.io/blog/archive/2026.md) ## Blog / Categories - [Guides](https://cpp-linter.github.io/blog/category/guides.md) ## Other pages - [Moving to cpp-linter from other clang-format and clang-tidy actions](https://cpp-linter.github.io/blog/posts/2026-09-12-moving-to-cpp-linter.md): Replace a clang-format check and a clang-tidy review job with one cpp-linter-action step, input by input. - [One clang-format version everywhere: pre-commit, CI and your laptop](https://cpp-linter.github.io/blog/posts/2026-09-12-one-clang-version-everywhere.md): Use the same LLVM major version for clang-format and clang-tidy in pre-commit, in cpp-linter-action and on your laptop, and upgrade it in one commit. - [Set up a clang-format pre-commit hook for C and C++](https://cpp-linter.github.io/blog/posts/2026-09-20-clang-format-pre-commit-hook.md): Set up a clang-format pre-commit hook for C and C++: pin the clang-format version, format only your own code, reformat an existing code base once, and enforce the same check in CI. - [Run clang-tidy on pull requests with GitHub Actions](https://cpp-linter.github.io/blog/posts/2026-09-20-clang-tidy-pull-requests-github-actions.md): Run clang-tidy on every pull request with GitHub Actions: generate compile_commands.json, report only the changed lines, post findings as review comments, and fail the check. - [clang-format changed under you: ubuntu-latest is now Ubuntu 26.04](https://cpp-linter.github.io/blog/posts/2026-11-09-ubuntu-26-04-clang-format.md): After ubuntu-latest moved to Ubuntu 26.04, the runner's default clang-format went from 18 to 21 and format checks started failing on unchanged code. Pin the version in your repository.