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 Overflow
🌐
Git 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:
Discussions

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
🌐 answers.netlify.com
3
0
October 4, 2021
Don't crawl history with git lfs push --all
Hi! Thanks for your work, really like Git LFS :) The issue The first git push after an LFS migration on a big repository may take several hours or days to complete, seemingly stuck while uploading ... More on github.com
🌐 github.com
16
December 20, 2020
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
🌐 stackoverflow.com
Help with Git LFS
What is your use case for storing videos in azure devops? More on reddit.com
🌐 r/azuredevops
17
2
September 11, 2024
🌐
Medium
medium.com › junior-dev › how-to-use-git-lfs-large-file-storage-to-push-large-files-to-github-41c8db1e2d65
How to use Git-lfs ( Large File Storage ) to push large files to Github - Junior Dev - Medium
November 20, 2020 - Step 4: Select the file types that you want Git-lfs to manage using the command git lfs track “*.csv” , this creates a .gitattributes file. Step 5: Add the .gitattributes file along with other files which need to be committed and push the changes.
🌐
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
🌐
GitHub
docs.github.com › en › repositories › working-with-files › managing-large-files › configuring-git-large-file-storage
Configuring Git Large File Storage - GitHub Docs
To associate a file type in your repository with Git LFS, enter git lfs track followed by the name of the file extension you want to automatically upload to Git LFS.
Find elsewhere
🌐
Atlassian
atlassian.com › git › tutorials › git lfs
Git LFS - large file storage | Atlassian Git Tutorial
January 12, 2026 - 2. When you push new commits to the server, any Git LFS files referenced by the newly pushed commits are transferred from your local Git LFS cache to the remote Git LFS store tied to your Git repository.
🌐
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 ...
🌐
DEV Community
dev.to › unegbuclinton › how-to-push-large-files-to-git-repository-using-git-lfs-5db3
How to push large files to git repository using Git LFS - DEV Community
September 30, 2024 - git add .gitattributes git commit -m "Track large files using Git LFS" 4.Add and Push Large Files: Now, when you add a large file (e.g., a video or image), Git LFS will automatically manage it:
🌐
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.
🌐
Netlify
answers.netlify.com › support
Git LFS - correct way to push new files? - Support - Netlify Support Forums
October 4, 2021 - 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.
🌐
PhoenixNAP
phoenixnap.com › home › kb › devops and development › git lfs: how to push large files to git repo
Git LFS: How to Push Large Files to Git Repo
July 18, 2025 - When you add a tracked file to ... data locally. Pushing a commit causes the LFS client to upload any new large-file data from the local cache to the remote LFS store associated with the repository....
🌐
Josh-Ops
josh-ops.com › posts › add-files-to-git-lfs
Adding Files to Git LFS | josh-ops
January 27, 2026 - Once you track the file(s) you want to add to LFS with the git lfs track command, you simply have to stage with git add, commit, and push as normal.
🌐
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 ...
🌐
GitHub
github.com › git-lfs › git-lfs › issues › 4350
Don't crawl history with git lfs push --all · Issue #4350 · git-lfs/git-lfs
December 20, 2020 - When we're pushing a repository that's newly rewritten, we're going to traverse every blob that exists that's less than 1024 bytes so that we can determine if an LFS object is in that object. This explains why git push takes a very long time processing LFS objects on this repo, if it has to go through all 700K Git objects, 100 by 100, to determine whether or not they are LFS objects.
Author   git-lfs
🌐
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