api VS lovely-forks

It helps you effectively find a file within your code by calling a plugin based on the file type, which then executes a regular expression on the source code to detect import statements. Meanwhile, it uses GitHub tree API in your browser to resolve related file references. Similarly, it uses the OctoLinker API to resolve the external dependencies using the dependency's name and the registry type.

>One problem is discoverability. GitHub lists forks in an un-sort-able manner.

This obviously doesn't solve the problem generally, but I recently found an extension called lovely-forks[1], that automatically shows the most starred fork for every github repository.

1:https://github.com/musically-ut/lovely-forks

The post resonates with me as an OSS user and a contributor. Many a brave souls have taken to forking the project to fix the bugs but those forked projects almost always suffer from a discoverability problem. I have tried making fixes and tried forking projects only to discover that someone else has done it better elsewhere.

I've been burned by this problem often enough that I wrote a Chrome extension which would _tell_ me if there are any notable forks of the project I'm currently looking at on GitHub: https://github.com/musically-ut/lovely-forks .

Lovely forks is a chrome add-on built to bring your notice to notable forks (i.e., forks with the most stars) for GitHub projects. It helps to keep track of the community-appreciated fork by adding a subscription under the repository's name on the Github page of all projects with a link to that fork.