tfnico's blog

Wow, nearly a year since my last post. I was sort of thinking it would be something more profound, but here goes: Git recently (with version 2.3) introduced a way of easily pushing changes into a remote non-bare repository, a.k.a. push-to-deploy . The old way would be to have a post-receive hook run some update logic which would do some procedure to update a non-bare repository. There now is a simple way of configuring the target repository to update its work tree instead  upon being pushed to. Now, pushing to the target repo may fail in cases where it has been modified, so soon after, a new push-to-checkout  hook was introduced  to deal with this, but it will only take effect in Git 2.4. I'll show how to set up both below. Surprisingly, when searching for "push-to-checkout", I found very few articles about this, even though it was loudly mentioned on the GitHub blog  ( twice , and on StackOverflow , of course ). So here's another one for the googles. Besides, ...