GIT-LFS-POST-CHECKOUT(1)
π NAME π
okay so welcome to the git-lfs-post-checkout manual page, bestie β this is the GIT-LFS-POST-CHECKOUT(1) page, and it's literally just the Git post-checkout hook implementation. that's the whole vibe. π
β¨ SYNOPSIS β¨
git lfs post-checkout <rev-before> <ref-after> <is-branch-checkout>
three arguments, no cap. don't skip any of them. π
π DESCRIPTION π
so this thing responds to Git post-checkout events β like, that's its whole job and it does it slayfully. π¦
what it actually does: it makes sure that any files which are marked as lockable by git lfs track are read-only in the working copy β but only if they're not currently locked by the local user. so if you're the one holding the lock, you get to keep editing, periodt. if you're not? read-only. π₯
fr fr bestie: this is why your lockable files sometimes go "nope, can't touch this" after a checkout. it's not a bug, it's this hook doing its main character work. π
π¦ SEE ALSO π¦
git-lfs-track(1)β go read it, it's giving "the one who marks stuff lockable" π
and this page is part of the git-lfs(1) suite, so there's a whole fam around it. π«Ά
that's the whole page, babes β nothing else hiding in here. the footer just repeats GIT-LFS-POST-CHECKOUT(1) at the bottom like a little echo, and honestly? iconic. no extra source/version or date info was dropped in there, so this is the entire tea. ββ¨πΈ
π¦ where this page comes from
- arch rolling: git-lfs 3.8.1-1 Β· MIT
- nixos 26.05: git-lfs 3.8.1
- nixpkgs unstable: git-lfs 3.8.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms