GIT-LFS-PRE-PUSH(1)

πŸ’– NAME πŸ’–

git-lfs-pre-push β€” Git pre-push hook implementation. Hii bestie, welcome to the GIT-LFS-PRE-PUSH(1) manual page β€” yes, this is the git-lfs pre-push hook page, and it’s lowkey iconic. πŸŽ€

✨ SYNOPSIS ✨

Run it like this, no cap:

git lfs pre-push <remote> [remoteurl]

πŸ¦‹ DESCRIPTION πŸ¦‹

It responds to Git pre-hook events. It reads the range of commits from STDIN, in this exact format:

<local-ref> SP <local-sha1> SP <remote-ref> SP <remote-sha1> \n

It also takes the remote name and URL as arguments.

If any of those Git objects are associated with Git LFS objects, those objects will be pushed to the Git LFS API. The way that works is very much giving β€œLFS handles its business.” πŸ’…

In the case of pushing a new branch, the list of Git objects will be all of the Git objects in this branch. In the case of deleting a branch, no attempts to push Git LFS objects will be made β€” literally none, periodt.

πŸ’… OPTIONS πŸ’…

  • -d, --dry-run β€” Print the files that would be pushed, without actually pushing them. It’s a preview era, bestie. πŸ‘€
  • GIT_LFS_SKIP_PUSH β€” Do nothing on pre-push. For more information, see git-lfs-config(5).

🌈 SEE ALSO 🌈

Part of the git-lfs(1) suite.


Sign-off time: the footer in the source is just GIT-LFS-PRE-PUSH(1) again, with no source/version or date attached, so I’m not inventing either β€” just sending you off with the vibes and the facts intact. Stay slay, bestie. πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from