Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add externalInclude information to compilation_context
Hi bazel team I use an aspect to run clangtidy on the codebase. It is based on https://github.com/erenon/bazel_clang_tidy. To check my codebase with `-Werror`, I use the "new" feature `external_include_path` requested by #12009, introduced by commit 08936ae. Now my clangtidy rules did not work anymore of course. As you can see in https://github.com/erenon/bazel_clang_tidy/blob/master/clang_tidy/clang_tidy.bzl, all the different include paths are being passed to the clang-tidy executable. I now also needed to pass the new external_includes to `clang-tidy`. This PR adds `external_includes` to the `compilation_context` object. I looked at the style of the other `includes` and hope it is in line with your expectations. Closes #18094. PiperOrigin-RevId: 548070112 Change-Id: I212420d2f888c3af088c4afbf8202c848d19722e
- Loading branch information