Replies: 2 comments 1 reply
-
Yes, it's kind a limitation of the This is because these data are fetched from GitHub Api instead of being computed To make them more accurate (including for personal repo), one would need to iterate through all commits history to filter out a single user commit and then run github/linguist on it to get stats (the Because of the rate limit it's not possible to do it on the fly (users with thousands of commit will reach the limit quickly), but I can see something working with a cache system. I know other users whi have been requesting this, I may give it a shoot next week 🙂 |
Beta Was this translation helpful? Give feedback.
-
v3.10 will integrate a
It's still experimental and some huges patches may be skipped but it should still yield nice results (I hope 😅) Also, a new |
Beta Was this translation helpful? Give feedback.
-
If I have not missed anything, I couldn't find an option to include languages I contributed to the repositories of other people(not the whole repositories, just my commits).
Beta Was this translation helpful? Give feedback.
All reactions