Confusing metric result for used languages #1047
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
For the lack of Rust detection, it's most likely related to #551 (see #551 (comment) for my theory why this is happening, but it's basically a combination of |
Beta Was this translation helpful? Give feedback.
-
The aim behind But to recap quickly:
So as stated above, ideally if a public repo contains let's say rust and typescript and you've worked only on rust code, the end goal is to "leave out" typescript from your stats since you didn't really author it. As for private repos, another user reported this issue too, it may be an actual bug but I haven't investigated too much on it yet
Most likely @spenserblack is correct. Indepth mode should not have the issue though (so needs to investigate on this too), but for recently used languages it's kind of normal. The way recently used language works is to fetch "git patches" from your activity feed, it doesn't actually look at the whole file or repository, it just perform the languages analysis on code snippet so it may be lacking the required context so github linguist is able to accurately determine the used language. Maybe a workaround would be to load the entire file to get the languages and then evaluate the patch I'm not sure the linguist api provides it, but maybe if we could pass "weights" to heuristics it could mitigate the issue too.
This one is bit tricky, but only repositories that were fetched by the base plugin (which depends on If you let the default settings, then only repositories that you own (and are not forks) are analyzed. Hopefully this is a bit more clear and it's helpful 😅 |
Beta Was this translation helpful? Give feedback.
-
Fantasitc reply Mr. makes it already more clear then I had expected. Thanks alot. |
Beta Was this translation helpful? Give feedback.
The aim behind
indepth
mode is mostly explained here but let me know if it isn't clear enoughBut to recap quickly: