21fe764027
It is sometimes useful to allow temporarily disabling Git LFS functionality when doing git push, for example when pushing to a remote that doesn’t support Git LFS. This fixes the issue #3721. Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>
36 lines
892 B
Markdown
36 lines
892 B
Markdown
git-lfs-pre-push(1) -- Git pre-push hook implementation
|
|
=======================================================
|
|
|
|
## SYNOPSIS
|
|
|
|
`git lfs pre-push` <remote> [remoteurl]
|
|
|
|
## DESCRIPTION
|
|
|
|
Responds to Git pre-hook events. It reads the range of commits from STDIN, in
|
|
the following 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.
|
|
|
|
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.
|
|
|
|
## OPTIONS
|
|
|
|
* `GIT_LFS_SKIP_PUSH`:
|
|
Do nothing on pre-push. For more, see: git-lfs-config(5).
|
|
|
|
## SEE ALSO
|
|
|
|
git-lfs-clean(1), git-lfs-push(1).
|
|
|
|
Part of the git-lfs(1) suite.
|