Skip to content

Conversation

bavulapati
Copy link
Contributor

clang-tidy when the config is not explicitly mentioned in the command looks for it in the project directory with the name .clang-tidy. And editors like VS Code recognizes the .clang-tidy file when code analysis is enabled. This is not a fix for a bug. This is just trying to make clang-tidy config and usage more visible.

clang-tidy when the config is not explicitly mentioned in the command looks for it in the project directory with the name `.clang-tidy`.
And editors like VS Code recognizes the `.clang-tidy` file when code analysis is enabled.
This is not a fix for a bug. This is just trying to make clang-tidy config and usage more visible.

Signed-off-by: Balakrishna Avulapati <bavulapati@gmail.com>
Signed-off-by: Balakrishna Avulapati <bavulapati@gmail.com>
@bavulapati bavulapati force-pushed the move-clang-tidy-config-to-project-directory branch from d2a48d7 to 587aea5 Compare May 27, 2025 15:12
Signed-off-by: Balakrishna Avulapati <bavulapati@gmail.com>
@jviotti
Copy link
Member

jviotti commented May 28, 2025

Makes sense for this project, but keep in mind that other of my projects pull this repo as a dependency and re-use the same ClangTidy (and ClangFormat) config files. In those child projects, we would have the same problem, as the config files wouldn't be on the root.

As an alternative, is there a way we can commit Visual Studio Code config files or something to all repos to always point at the right config file locations, no matter where they are? There might be a way

@bavulapati
Copy link
Contributor Author

Not sure why DCO test is failing on the latest commit.

@bavulapati
Copy link
Contributor Author

not needed

@bavulapati bavulapati closed this Jul 16, 2025
@bavulapati bavulapati deleted the move-clang-tidy-config-to-project-directory branch July 16, 2025 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants