Bitbucket Best Practice for Template Repositories

[Epic River]

We are an active user of bitbucket and Atlassian hosted.

We have a project with a related repository that we use as a template for starting our new projects. Within Bitbucket, we have a template repository that is the starting point for new projects.

What would be the best practice for creating a new project off of this repository. If we fork, then it is nice to sync updated to the new repository before the project begins, and to get the project history, but we are concerned that in the future once the project has diverged if someone syncs it will cause damage.

The other possibility that we see is just copying the code, but then we lose the history and the ability to sync before the project begins.

What would be your recommendation for the best practice in this situation.

[Tom Gagne]

Have you come-up with a best practice? Forks are an interesting approach.

I would also like the service hooks to be copied--so I don't need to create those every time...

[Nic Winn]

This is a great question. Did you come up with anything @Epic River or @Tom Gagne?