Better way to package and distribute boilerplate

I love the work done so far to build and maintain this boilerplate. git (v >= 1.9) complains when cloning a shallow copy of this repo, then changing the remote URL and then proceeding to push to the updated remote. This means if I were to use this boilerplate for my own project I would

• either need to keep the commit history of this repo and build on top of it
• remove the .git folder and git init myself and push the new changes
• ZIP download the contents, and then go a similar route as the one above

… I don’t really like either 😅

I was wondering if there is a way to package and distribute this boilerplate, much like an npm package?

Thanks for all the hard work! 💖

[yeskunall]

I fully understand that 😅thanks for being open to the idea — even if it’s not viable in the near future! @amilajack

[syddo]

I’m not sure if this will be an acceptable alternative but in my case I did:

git remote remove origin
git rev-parse --verify master >> .git/info/grafts
git filter-branch -- --all
rm .git/shallow
git remote add origin <new-git-repo-url>
git push origin master

It worked okay and started a new git project.