-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Innaccuracies with language plugins stats #531
Comments
Other issues:
|
@Napolitain Could you try setting |
@lowlighter I have tried regenerating token before I saw your response, which turned out to be an error (it logs less total commits), then tried your suggestion. It is clearly better, but still lacking commits. Now I'm at 345 commits analyzed of 955 total. |
Ok so I removed "indepth" and it seems better representative of the repositories. I think that's linked to what you describe in this issue, as it shows only current state. And I think it reads the last commit of each file (or something like that) so only few lines are registered (and not the whole file). |
Superseded by #857 |
While investigating on #513 I noticed some flaws in the languages plugin.
It is actually not very well defined whether it should count your effective language stats (meaning stats from the current state of each repo) or cumulative language stats (meaning stats should include previous state of each repo, including code that has been refactored, moved or deleted).
Currently, the languages indepth analyzers is doing the following:
git log --patch
on each user commit to find which lines were added by user and update bytes count using detected language by linguistFor now, it leans more toward cumulative stats rather effective stats.
Since tracking deleted files is currently impossible because they don't exist when linguist analyze the repository (so detected language for a deleted file is always
null
), deleted/moved files are never taken into account so some lines are actually lostAlso renamed file may be counted multiple times, need to check whether an option exists to detect them (maybe
--follow
?)The text was updated successfully, but these errors were encountered: