Re: git push from client is not updating files on server
From: Jerome Yanga <hidden>
Date: 2016-06-15 22:53:14
Thank you all for the recommendations. I will try them. I would like to confirm some info. Junio, Your assumption of my setup correct. I shall read on post-update hook. If you have a recommended link for it, please share it. Neal, You are also correct. My current configuration's reaction to a push shows that the bare repo that was cloned from a non-bare repo are independent of each other. I will also try your recommendation. Holger, Thank you for explaining what Neal meant. Regards, j On Wed, Mar 7, 2012 at 3:04 AM, Holger Hellmuth [off-list ref] wrote:
On 07.03.2012 03:34, Neal Kreitzinger wrote:quoted
Create a new non-bare clone of your bare repo. Then do git-pull on the new non-bare after the bare gets updates (someone does git push to it) and you want to test those new commits. The worktree of the new non-bare clone can be the document root of your testing virtual host, if that's what you're doing. That way, you know that no one else is messing with new non-bare (test repo) like doing development in it and messing up your tests.To expand on Neals method, if you do git fetch (periodically in a cron job for example) on the cloned non-bare, 'git log HEAD..origin/HEAD' will have output only if the non-bare has new commits.