Using gitlab/github.
I created boilerplates for all my projects so I’ve:
wordpress-boilerplate
html5-boilerplate
laravel-boilerplate
ror-boilerplate
I’m debating myself if/when starting a new project I should fork boilerplate and thus save the relationship, or simply export boilerplates and push them to projects own repo.
What is your take on this?
I feel forking is not necessary since I wouldn’t be pushing anything back to boilerplates.
Sometimes I think about such unimportant things 🙁
3
If you’re building a one-off application, I’d recommend cloning the boilerplate, renaming, and building from there.
If you’re going to be doing that a lot, and especially if you find yourself starting from the same boilerplate each time but adding certain features repeatedly, then fork the boilerplate, add improvements to your fork, and start new app development projects from your fork of the boilerplate.
The latter has been my approach working with the Roots theming framework for WordPress projects, for instance. I’ve got my own fork of Roots to which I’ve added some handy features of my own, and I start new theming projects from my fork.
1