Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

MacOS M1 - Git LFS files not uploading with push but works fine pushing on windows

Rob Farthing
Rob Farthing Nov 26, 2021

On windows sourcetree using embedded git and git lfs all is working fine, but on mac OS using sourcetree with embedded git and git lfs, only the non lfs files go up.

I have to open the terminal in sourcetree and type git lfs push --all origin master after every push from Sourcetree.

I have been using Sourcetree on macs and windows for years, this is a new M1 mac I have installed Sourcetree on and this has only just occurred recently.

Using Sourcetree mac on M1 mac mini - Sourcetree version 4.1.3 (239) and git embedded 2.31.0 and git lfs embedded 2.13.2

Is anyone else having this issue? I tried a fresh install with removal of all preferences files from the Library folder also.

Answer
Watch
Like Be the first to like this
1392 views

1 answer

1 accepted

1 vote
Answer accepted
Rob Farthing
Rob Farthing Nov 26, 2021

Closing this now as I found the cause was some badly generated git hooks files, a fresh clone of the repo sorted it out. Leaving this issue up in case it helps others in this strange scenario I had.

Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS
AUG Leaders

Atlassian Community Events

See all events