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've managed to successfully clone a couple Azure DevOps repositories using Sourcetree, but I'd like to make sure I'm using Git LFS with them so that I'm properly managing binary files.
I found the Git LFS menu in Sourcetree under Repository > Git LFS, and I selected Initialise Repository. I'm using this workflow to develop for Unreal Engine, so I added two types of files to track to start: *.umap and *.uasset.
To be clear, I didn't know Git LFS wasn't setup by default, so I initialized the repository after I had received a warning that one of my *.umap files was over 10 mb in size. Once I initialized Git LFS and started tracking the specified file types, I noticed that the *.umap file was staged with both a + and - sign, which is different than how it usually looks when committing.
Does this indicate that it's working properly? I'm new to managing non-code related files using Git, and from what I've read, Git LFS seems like a powerful way to manage large files, so any help understanding this would be helpful.
Thanks!
It appears that it's working correctly. I tried adding some larger files to test it, and I saw the log below when showing full output on commit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.