I faced the same issue like you. After I did follow this guide and original guide, the bug is fixed. Please remove large files in git add . and redo:
git reset --hard
git lfs install
git lfs track "*.psd"
git add .gitattributes
git add file.psd
git commit -m "Add design file"
git push origin main
Answer from M.Vu on Stack OverflowGit LFS
git-lfs.com
Git Large File Storage | Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
To do that, use the git lfs migrate(1) command, which has a range of options designed to suit various potential use cases. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named main:
Git LFS - correct way to push new files?
Love the feature 🙂 Today I added about a hundred more, totaling maybe 100MB. Before I pushed, I ran a git lfs status and saw the correct set of files reported as “Git LFS objects to be pushed to origin/main”. And after a git push, git lfs status returned a clean result. More on answers.netlify.com
git lfs - Force push a git lfs file ID - Stack Overflow
Using git lfs, how can I force push a file ID that I know I have locally but that for some reason did not get pushed to the server ? ie, on my build system I have errors like Git LFS: (0 of 15 ... More on stackoverflow.com
Help with Git LFS
What is your use case for storing videos in azure devops? More on reddit.com
My files are not uploading to LFS
I tracked all the .tga and .TGA files with git lfs track "*.tga"but it doesn't upload my files to lfs at all. The files appear in git lfs track and the extension is added in .gitattributes · $ git add "*.tga" $ git commit -m tga $ git push origin main Enumerating objects: 1774, done. More on reddit.com
Videos
07:55
How to Setup Git LFS for New and Existing Projects (Works With ...
06:51
How To Install and Use Git LFS to Version Control Large File Projects ...
04:09
GitHub upload large files | Push your large file to github | git ...
How To Install and Use Git LFS to Version Control Large File ...
04:09
GitHub upload large files | Push your large file to github | git ...
Debian Manpages
manpages.debian.org › testing › git-lfs › git-lfs-push(1)
git-lfs-push(1) — git-lfs — Debian testing — Debian Manpages
This pushes all objects to the remote that are referenced by any commit reachable from the refs provided as arguments. If no refs are provided, then all local refs are pushed. Note that this behavior differs from that of git-lfs-fetch(1) when its --all option is used; in that case, all refs ...
Anchorpoint
anchorpoint.app › blog › push-and-pull-files-with-git-lfs
Push and pull files with Git LFS - Anchorpoint
February 12, 2026 - The easiest way to configure Git LFS is to download this .gitattributes file, which was configured to work with Unreal and Unity Engine, and place it in the root folder of your Git repository. Then use a desktop application like SourceTree, Fork, or Anchorpoint that supports Git LFS to push and pull files.
GitHub
github.com › git-lfs › git-lfs › blob › main › docs › man › git-lfs-push.adoc
git-lfs/docs/man/git-lfs-push.adoc at main · git-lfs/git-lfs
This pushes all objects to the remote that are referenced by any commit reachable from the refs provided as arguments. If no refs are provided, then all local refs are pushed. Note that this behavior differs from that of git-lfs-fetch(1) when ...
Author git-lfs
ManKier
mankier.com › home › git-lfs
git-lfs-push: Push queued large files to the Git LFS endpoint | Man Page | Commands | git-lfs | ManKier
This pushes all objects to the remote that are referenced by any commit reachable from the refs provided as arguments. If no refs are provided, then all local refs are pushed. Note that this behavior differs from that of git-lfs-fetch(1) when its --all option is used; in that case, all refs ...
Atlassian Support
support.atlassian.com › bitbucket-data-center › kb › the-initial-push-to-a-git-repository-with-git-lfs-enabled-takes-a-long-time
The initial push to a Git repository with Git LFS enabled takes a long time | Bitbucket Data Center | Atlassian Support
April 2, 2025 - Push the repository by running git push --force (this should complete quickly) ... This will return the Git LFS objects id to be pushed.
GitLab
docs.gitlab.com › topics › git › lfs
Git Large File Storage (LFS) | GitLab Docs
In the root directory of your local copy of the repository, run git lfs install. This command adds: A pre-push Git hook to your repository.
Ncloud-docs
guide.ncloud-docs.com › docs › en › sourcecommit-use-lfs
Using large file system (LFS)
$ git lfs track "*.psd" Tracking "*.psd" $ git add .gitattributes · Commit large files to be uploaded. Push the files to the remote repository.
Lsst
developer.lsst.io › git › git-lfs.html
Using Git LFS (Large File Storage) for data repositories — LSST DM Developer Guide main documentation
Go to https://roundtable.lsst.cloud/settings/tokens and request a token with scope write:git-lfs. It would be best practice to request a token with a finite lifetime, but on your own conscience be it if you ask for one that never expires. Copy that token, because this is the only time Gafaelfawr ...
Arfc
arfc.github.io › manual › guides › git-lfs
Git Large File Storage
ARFC Git Large File Storage is quite large, but be respectful to your colleagues and make sure you store only valuable data of reasonable (100Mb-5Gb) size. Consider using alternative storage options such as Box if version control is not necessary or if files of a larger size need to be stored. ... Do it from the top level directory of the repository. Success! Just commit and push to GitHub as you normally would
Top answer 1 of 2
22
I managed to trigger some extra documentation somehow.... the syntax is actually
git lfs push origin --object-id [ID]
And it will force sync an object that a simple git lfs push would not
2 of 2
12
I had errors on my build system after migrating a repository and it's pipeline to a new remote. I deleted the repository on the old remote before migrating the LFS data (which I forgot existed). When the pipeline ran, I was seeing errors such as
fetch: Fetching reference f0e482d67ea35e173e15a22c0bacb37f2c059365
[b898bde8bb8ee3ee58390ec930e8608568920f61cc9954f198bdacdf79e0d7a8] LFS object not found: [404] LFS object not found
[112e9f3c1dba98d5cafcaadbf2a34dda733a4175632c0d4ba3dbfc590d95ffd4] LFS object not found: [404] LFS object not found
[dd8066b545c4fb09057ace1cf6c6fb8df41b89647c33b5f071d38255da7539ed] LFS object not found: [404] LFS object not found
error: failed to fetch some objects from '<redacted>.git/info/lfs'
##[warning]Git lfs fetch failed with exit code 2, back off 5.225 seconds before retry.
Fortunately, I had the LFS data locally and was able to resolve via:
git remote rm origin
git remote add origin <new_remote_url>
git lfs push origin --all