Bitbucket Best Practice for Template Repositories

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.

1 answer

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...

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

287 views 38 9
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot