On 16 June 2015 at 13:08, Chad Baloga <cbal...@gmail.com> wrote:
> I am fairly new to GIT.  When we do a push to the remote repo, the Working
> Copy on the remote does not get updated automatically.  It shows the
> changes, then we have to either discard the changes or stash them.  If this
> normal or is there a way it can automatically update?  We have 2 branches.
> At first there was only 1 branch.  Thanks!

I'm not sure I fully understand your question, but git wil *never*
update Working Copy A just because someone pushes changes from Working
Copy B.  The standard answer when someone asks for this is that *git
is not a deployment tool*!

(The reason I'm not sure that I understand the question is the words
"then we have to either discard the changes or stash them".  It's
unclear why you would commit and push in one working copy, then fetch
or pull in another just to discard the committed changes...)


Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to