Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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


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
Atlassian Team members are employees working across the company in a wide variety of roles.
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
AUG Leaders

Atlassian Community Events