branchdir lets tiobe know what is the root directory of the source files. By default, it's set to the root of the repository. In the case of monorepos that have multiple projects live under them, we want the branchdir to point to REPO_ROOT/CHARM_PATH so that it only takes into account the charm's own directory and not the other charms'.
Example. Here, although the scan is to run for tempo-worker, it's also taking the coordinator's directory into account, which lowers the quality score.
Thought: Even if we point only to the charm's directory, tiobe will include everything under that dir including the libs dir which gives a wrong indication when it comes to, for example, the test coverage of the charm's codebase. Should we maybe point branchdir to REPO_ROOT/CHARM_PATH/src
branchdirlets tiobe know what is the root directory of the source files. By default, it's set to the root of the repository. In the case of monorepos that have multiple projects live under them, we want thebranchdirto point toREPO_ROOT/CHARM_PATHso that it only takes into account the charm's own directory and not the other charms'.Example. Here, although the scan is to run for tempo-worker, it's also taking the coordinator's directory into account, which lowers the quality score.
Thought: Even if we point only to the charm's directory, tiobe will include everything under that dir including the
libsdir which gives a wrong indication when it comes to, for example, the test coverage of the charm's codebase. Should we maybe pointbranchdirtoREPO_ROOT/CHARM_PATH/src