Man page - git-lfs-post-commit(1)
Packages contas this manual
- git-lfs-pointer(1)
- git-lfs-config(5)
- git-lfs(1)
- git-lfs-checkout(1)
- git-lfs-post-merge(1)
- git-lfs-pull(1)
- git-lfs-lock(1)
- git-lfs-dedup(1)
- git-lfs-push(1)
- git-lfs-ext(1)
- git-lfs-uninstall(1)
- git-lfs-track(1)
- git-lfs-untrack(1)
- git-lfs-fsck(1)
- git-lfs-status(1)
- git-lfs-ls-files(1)
- git-lfs-completion(1)
- git-lfs-pre-push(1)
- git-lfs-update(1)
- git-lfs-clone(1)
- git-lfs-locks(1)
- git-lfs-clean(1)
- git-lfs-post-checkout(1)
- git-lfs-filter-process(1)
- git-lfs-smudge(1)
- git-lfs-env(1)
- git-lfs-merge-driver(1)
- git-lfs-fetch(1)
- git-lfs-migrate(1)
- git-lfs-post-commit(1)
- git-lfs-install(1)
- git-lfs-standalone-file(1)
- git-lfs-prune(1)
- git-lfs-unlock(1)
- git-lfs-logs(1)
Package: git-lfs
apt-get install git-lfs
apt-get install git-lfs
Manuals in package:
Documentations in package:
Manual
| GIT-LFS-POST-COMMIT(1) | GIT-LFS-POST-COMMIT(1) |
NAME
git-lfs-post-commit - Git post-commit hook implementation
SYNOPSIS
git lfs post-commit
DESCRIPTION
Responds to Git post-commit events. It makes sure that any files which are marked as lockable by git lfs track are read-only in the working copy, if not currently locked by the local user.
Where the git lfs post-merge command, which has a similar purpose, must examine all files in the working copy, git lfs post-commit can limit itself checking only those files which have changed in HEAD. It primarily handles newly added lockable files which have not yet been made read-only.
SEE ALSO
git-lfs-post-merge(1), git-lfs-track(1)
Part of the git-lfs(1) suite.
| 2025-06-22 |