lovely-forks
lovely-forks copied to clipboard
musically-ut
Show stars also at forked page
Currently, this plugin displays "the most prominent fork". When there are more than one potential forks, I would like to evaluate them... The best support for me would be to see the stars at all other forks at the fork page.
Example: https://github.com/chunksnbits/jquery-quickfit
I think, there is another "good" fork. How can I see it at the list of forks?
Hmm, that is an interesting idea.
The plugin does have at least part of that data (i.e. the first page sorted by stars) and it can be stored/refreshed in local storage.
I'll include it in the next iteration with a few other features.
Thanks!
PS: Link to the actual list of forks: https://github.com/chunksnbits/jquery-quickfit/network/members
Might also be worth removing stars by the author themselves from the count? IMO a fork with 1 star is pretty different to a fork with 1 star from the author of that fork.
Would it be possible to also include commit count in that list (ahead/behind of master) to see if it's actually being developed?
That is a good suggestion @dovry.
However, the commit count is misleading if there have been commits both on the original repository as well as on the fork, resulting in a divergence. Hence, Lovely Forks guesses which of the two repositories is more up to date by looking at the latest time they were pushed_at.
See #13 for a more detailed discussion behind this decision.
What I understand there are three feature requests in this ticket
- Show stats for a forked repo as well.
- Show stats on this page https://github.com/user/active-forks/network/members
- Show stats on this page https://github.com/user/repo/network/members I am more interested on number 3 , and more importantly, I am interested in number of commits as well (not just stars), many times I want to see all repos who have forked from mine and have gone many commits ahead of the parent repo but yet have not sent any pull requests, So those changes never get noticed and people working on the parent have to redo all those. For example, you won't get to know if anyone from here have already implemented these but have not sent you a pull requests unless you visit each of the forks and investigate.
