Why git lfs pre-push is ignoring its fourth stdin parameter (remote revision sha1) while choosing objects to send?

Instead it uses git rev-list --not --remote <remote> which could find too many objects if remote is not registered in git (or not fetched into refs/heads/remote/*)

I'm using git automation without any named remotes, so my git push starts to fail because of missing objects in the lfs cache. Seems like such failures were just fixed in #3634, but this solution still requires processing all objects ever been in repo.

Is it possible to consider remote revision sha1, excluding reachable revisions from it?