Skip to content
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

Consider detaching the repository from upstream #2

Open
vpavic opened this issue Mar 19, 2024 · 4 comments
Open

Consider detaching the repository from upstream #2

vpavic opened this issue Mar 19, 2024 · 4 comments

Comments

@vpavic
Copy link

vpavic commented Mar 19, 2024

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
Copy link
Member

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
Copy link
Author

vpavic commented Mar 21, 2024

Thanks, I was able to fork the repo now.

Any feedback on the history cleanup proposal?

@jamesward
Copy link
Member

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

@dsyer
Copy link

dsyer commented Mar 21, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants