git-annex-post-receive(1)

πŸ“¦
version 10.20261026 Β· 3 versions
, in alpine 3.24, arch rolling, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– git-annex-post-receive πŸ’–

okay bestie, this is the manual page for git-annex-post-receive, and it lives in the git-annex General Commands Manual, so pull up a chair 🫢


✨ NAME ✨

git-annex-post-receive β€” the thing that gets run by the git post-receive hook πŸ‘‘


🌸 SYNOPSIS 🌸

git annex post-receive

πŸ¦‹ DESCRIPTION πŸ¦‹

So the whole vibe here is: this is meant to be called from git's post-receive hook. You don't usually summon it yourself. git annex init automatically creates a post-receive hook that uses this, no cap β€” it just does it for you πŸ’…

Now, here's the tea β˜• when a repository is configured with receive.denyCurrentBranch=updateInstead, pushes to that repository update its work tree. Cute, right? But β€” and this is the important part β€” that does not work for repositories that have an adjusted branch checked out 😭. That's exactly where this hook comes in: it updates the work tree when it's run in such a repository, and it does the same thing as running git-annex merge would. Same energy, same result ✨

And there's more πŸ’– when a repository is configured to proxy to a special remote with exporttree=yes, and the configured remote.name.annex-tracking-branch is received, the hook handles updating the tree exported to the special remote. Iconic behaviour, honestly 🌈


πŸ’… OPTIONS πŸ’…

  • The git-annex-common-options(1) can be used. that's the whole options section, bestie β€” go read the common options page for the full menu πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘


πŸ“ AUTHOR πŸ“

Joey Hess <id@joeyh.name> β€” absolute legend, no notes πŸ’œ


and that's the whole page, fr fr πŸ’– it's git-annex-post-receive(1) from the git-annex General Commands Manual, and this cutie was written by Joey Hess <id@joeyh.name>. slay, go update some work trees 🧚✨