Closed HerrTamm closed 3 years ago
First thing that comes to mind is to clear the log files before running the analysis. code-forensics does not execute the git log command again if it finds a log already generated for the exact same period of time (this is in order to save time). However if you happen to have changed the repository paths configuration you may have changed the file path selection criteria, hence you probably want to re-generate the log dump to include/exclude commits for files matching your configuration
Hey I just released an update that could help, as it provides the ability to force the vcs log generation when running an analysis (see the wiki)
closing due to no response/follow up.
We are using Lerna for a multi-package monorepo. There are multiple subdirectories in
packages/
directory, each containing the same base NodeJS project structure with source code having undersrc/
, except that.git/
directory is only in the root path.Only one of the packages is rendered correctly.
Output:
Config:
Job logs: