Check whether a commit is pushed before choosing a large-file fix
Run git ls-remote origin to see what the remote holds, and git log origin/main..HEAD to see unpushed commits. If the remote is empty or the big files exist only in unpushed local commits, a gitignore plus amend is enough. Only pushed history needs filter-repo/BFG or Git LFS migration, which is far more invasive.
Verified with a local bare remote on git 2.39.5: after
git rm --cached+git commit --amendof an unpushed commit,git pushsent no trace of the file (git cat-file -t <blob>in the remote: could not get object info), whereas fixing it with a NEW commit pushed the blob. Locally the old commit lingers in the reflog (git log --reflog -S'<text>'finds it,git log --all -Sdoes not) but it is not pushed. For several unpushed commits,git reset --soft origin/main+ recommit worked the same way.