Consider detaching the repository from upstream

[vpavic]

This repository has an awkward setup where it's created as a fork of dsyer/webjars-locator-core which in turn is a fork of webjars/webjars-locator-core (which itself is a fork, but that's not relevant here).

Other than being awkward, this actually prevents contributors from having forks of both webjars-locator-core and webjars-locator-lite (as the latter itself is a fork of the former).

Additionally, IMO there's no reason for webjars-locator-lite to inherit the entire history of webjars-locator-core (tags included).

So, my suggestions for this repository are:

• use detach a fork option from here to detach from upstream
• rewrite history (and force push it to remote) before the project gains more traction

[jamesward]

Oh! Well that explains why I haven't been receiving notifications for this repo. :) Thanks for pointing this out. I've made a detach request.

[vpavic]

Thanks, I was able to fork the repo now.

Any feedback on the history cleanup proposal?

[jamesward]

Let's see what @dsyer wants to do with the history.

[dsyer]

I don't care about the history really. My fork of core still exists if anyone wants to see it.