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.
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.