Ah, Thank you, thank you!
This bit did the trick:
I'm the only dev, so I can make sure the remote has no changes in the
working tree, but I can see now how the post-commit hook would kick it
off just right. Thanks for the pointer in the right direction.
On Jun 1, 2:50 pm, Konstantin Khomoutov <khomou...@gmail.com> wrote:
> On Jun 1, 9:06 am, ben <bklo...@gmail.com> wrote:
> > I've created a clone (lets call it Dev) of local project (Core), and
> > want to create a remote repo of Dev on a server (Staging) with a
> > working tree (the actual files).
> > How do I setup the remotes so that I can push from Dev to Staging?
> > Is this the wrong way to do it? Should I also have a bare repo on the
> > server as origin for everything, then just checkout a staging branch
> > when in Staging?
> > The catch here is that I've created Core locally, so I can start a new
> > project and have all the benefits of Core, and get updates by pulling
> > when Core itself is updated.
> Looks like you should read this
> And this subject has been raised more than once here, so may be a
> little searching through the history could yield more solutions.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at