Swastik Pal
Swastik Pal
There was an error in my earlier implementation. See the differences below: - Has error - [](https://github.com/kitswas) - Current - [](https://github.com/kitswas) Preview Deployment URL - https://github-readme-stats-l34h9pi63-kitswas.vercel.app
> From my first impression, the `y` variable (i.e. the number of repositories) influences the percentages. By running an optimisation on the `p` and `q` factors, we might get better...
The new commits - - [x] Rewrite the program in a way that disables the new behaviour by default. - [x] By default disable the influence of `y`. - [x]...
Resolved conflicts and rebased this branch onto [anuraghazra/github-readme-stats/master](https://github.com/anuraghazra/github-readme-stats/tree/master).
@mccarthyp-snet Well, I did get it done. See https://github.com/kitswas/github-desktop/commit/45388c9571a2ea46a5e866c4aa1c10f5f03bd0de I build and use it myself. I didn't create a pull request due to https://github.com/desktop/desktop/issues/10068#issuecomment-682960430 EDIT: You reminded me, it's probably...
Rebased. See https://github.com/kitswas/github-desktop/tree/checkout-a-commit
Requesting review for PR #16120.
Pulled latest changes from [anuraghazra/github-readme-stats/master](https://github.com/anuraghazra/github-readme-stats/tree/master).
@rickstaa Thanks for your continuous support. I wonder if we should change the names `p` and `q` to `size_weight` and `count_weight`, respectively. `p` and `q` are not exactly intuitive.
Users can also list by commit count and by size separately. This effectively removes ambiguity and confusion. For reference, here's how mine looks:  ![Top Langs By...