> Warning: doing "git push" to a non-bare repository is generally not recommended
Very true, my mistake for not being specific here. I do indeed use receive.denyCurrentBranch and it works like a charm. Thanks for the clarification. On Sun, Dec 4, 2016 at 2:57 PM Brian Candler <[email protected]> wrote: > On 04/12/2016 21:26, Jacob MacDonald wrote: > > The repository is not stored as bare; That way I can access the files > > in the repository directly from Drive > > Warning: doing "git push" to a non-bare repository is generally not > recommended, although you can do it with a post-update hook, or you can > use a feature introduced in git 2.3 called "push to deploy": > > https://github.com/blog/1957-git-2-3-has-been-released > > To use this, you have to set config "receive.denyCurrentBranch = > updateInstead" on the server copy of the repository. > > Otherwise: normally what happens is pushing to the repo updates the > objects in the repo but *not* the checked-out working copy, which can > get your repo into a very confusing state. See: > > > https://git.wiki.kernel.org/index.php?title=Git_FAQ&oldid=23811#Why_won.27t_I_see_changes_in_the_remote_repo_after_.22git_push.22.3F > >
_______________________________________________ Password-Store mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/password-store
