You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running rubycritic on large repositories with many years of commits can take > 30 minutes. I traced this down to the churn calculation. It is currently hard-coded to run git log on . which can be very expensive depending on the codebase.
For example, in mono-repositories with multiple projects and/or with multiple languages/frameworks it makes more sense to target RubyCritic's analysis to specific directories.
Running
rubycritic
on large repositories with many years of commits can take > 30 minutes. I traced this down to the churn calculation. It is currently hard-coded to rungit log
on.
which can be very expensive depending on the codebase.For example, in mono-repositories with multiple projects and/or with multiple languages/frameworks it makes more sense to target RubyCritic's analysis to specific directories.
I added more information in this PR: #419
Thank you!
The text was updated successfully, but these errors were encountered: