-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
Show how many commits ahead a fork is from the original repo and view them #66
Comments
I have a similar use case. Simply showing a column with how many commits ahead and/or behind the original repository would eliminate 95% of the junk forks. I'm looking for forks that have implemented changes on top of the original. An outdated or identical fork is useless to me, and I would think these are not useful to most people searching for an active fork |
I use this site to find new, active forks of unmaintained apps. |
This actively maintained web app has this feature (and many more). |
That's great. |
and also add sorting function |
Part of the definition of "active fork" is that it has commits past the original repo, so I think it is important (it certainly is to me) to see how many commits ahead a branch is. It would be cool if I can see the commit messages that the new repo has that the old one doesn't.
This repo/library is not being maintained, but I can't even import the library because it relies on a dependancy that is not in the android runtime (anymore at least), so all I want is to find a fork that solved that issue. Many of them just forked it without adding any new commits, and it is several years old (which I don't care about, so long as it works), but I can't tell if anyone fixed that issue just by looking at the last commit. There are 377 forks, so it is not feasible to look through each one to see if it has any commits that solve that issue.
Maybe there should even be a condition for "new commit message contains phrase"... so I can search for "dependancy" or "JUnit" (the missing dependancy), etc.
The text was updated successfully, but these errors were encountered: