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
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
Sourcetree 4.0.2, macOS Catalina. System Git 2.30.0, embedded git-flow, git-lfs 2.13.2, Bitbucket media adapter 1.0.6.
I'm checking out a fresh copy of a large repository with binary files tracked with Git LFS and stored in S3. Sourcetree pulls the repository fine, recognizes it has Git LFS files, pulls those automatically, and then goes through a long process of creating new staged files to commit, one for every binary file tracked by Git LFS. This does not seem right and I am concerned that it is going to push binary files into the repository/history. Why is it doing this and is there a workaround? Thanks.
As a counterpoint, when I download the same repository in GitHub Desktop, it downloads the repository, downloads the binaries, and then is quiet and reports 0 changes.