You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I had to add 3 folders in order to track possible modifications even though we are only modifying a handful (they are the vendors folder where some customization may and does occur). Is there some way to speed up branch checkouts in this situation (over five minutes) or (I don't want to do this) should I zip up the entire thing and just put a zip file there.
Here is the approach we took to deal with this -
removed this information from the repository
place it in a new "by itself" repository since it changes bvery rarely, and is usually due to upgrades rather than configuration/customization modifications.
Hi @kishjtk,
Welcome to Atlassian Community!
There is no option in Git to "speed up" the branch checkout. Are you switching between two branches that have these new files on them? Or are you switching between one that have them and another that doesn't? You may want to consider doing a shallow clone of specific branches instead of cloning the full history. Have a look at this post regarding shallow clone, How to Use Git Shallow Clone to Improve Performance. You should also look and see if Git LFS is an option to be used, especially if you have files that are over 10Mb in size.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.