Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

It is convenient to create a second repo when your original repository is too big by time history? Edited

Hi devs, I work in a videogame project with Unity3D engine. There are 8 people working on it (modelers, animators, musicians, designers) but the commits history, has been raised, along the time with a lots of assets, a lots. Iterations to improve textures, audio, models and of course code.

I think original repo can be stored and create a second repo from the original last repo's commit.

I understand the benefits of having historial, but in the practice, old commits there are not used anymore and the repo is private for local development.

What are your experiences? thanks for your time.

1 comment

Roger Barnes Atlassian Team Jan 14, 2020

That's a valid approach to consider based on your circumstances. You'd want to be sure everyone's finished up on any branches they have open, or have a way to cut them over also.

Alternatively you may be able to prune the commit graph to reduce its size.

Instead, or as well, I'd recommend using Git LFS for storing large files. It doesn't reduce the overall repo size in general, but it does cut down a lot on how much gets cloned and pulled. You can even use various tools to rewrite the Git history and put those large files into LFS, while preserving history.

In every case, you'll need to coordinate any such changes with your team to all cut over dev environments, tooling etc at once.


Log in or Sign up to comment
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

652 views 7 4
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you