SUMMARY I take clang-tidy as an example to explain the situation. clang-tidy can be configured with a .clang-tidy config file. This file can be committed to the KDE project repo and shipped together with it. IDE like KDevelop can use this file to configure the clang-tidy checks. The developer does not need to configure anything. Ideally, the same checks that are performed on the gitlab CI system are performed also in KDevelop and the develper does not need to wait the CI build to figure out possible problems. It would be nice to have clazy be configurable with a config file to support the same workflow.