You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got the plugin installed and set up and all working nicely. I have set up Git LFS on my laptop (installed using Homebrew) and have the .gitattributes file in place. Everything works well when I push my content folder to the remote origin repo (on GitHub) from the command line (or using the Tower app).
However, If I use the push button on the Git Content panel screen, I get the following error (in a modal):
This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks'). error: failed to push some refs to 'github.com:myusername/myreponame.git'
The push fails and I have to use the command line to push instead.
I also have Git LFS on my production site (running on Ubuntu 24.04) and pushing from the panel works fine there, so it seems specific to my local site. Could it be something to do with LFS being installed with Homebrew?
The text was updated successfully, but these errors were encountered:
I've got the plugin installed and set up and all working nicely. I have set up Git LFS on my laptop (installed using Homebrew) and have the
.gitattributes
file in place. Everything works well when I push my content folder to the remote origin repo (on GitHub) from the command line (or using the Tower app).However, If I use the push button on the Git Content panel screen, I get the following error (in a modal):
The push fails and I have to use the command line to push instead.
I also have Git LFS on my production site (running on Ubuntu 24.04) and pushing from the panel works fine there, so it seems specific to my local site. Could it be something to do with LFS being installed with Homebrew?
The text was updated successfully, but these errors were encountered: