From: Harry Johnson <hidden> Date: 2016-06-15 22:50:26
Hi All,
So I have a central build repo from which we perform nightly builds.
Then my development repo is a clone of the build repo. The idea is
that after I am convinced that my changes in my development repo are
stable enough I push them to the build repo using git push.
This seems to work and I can see my changes when doing a git log from
the build repo. However, the actual working files have not been
updated nor can I figure out any way to get them updated. For instance
I have tried deleting one of the files that should be changed and then
doing a git checkout <file>. The changes are still not present. I have
tried doing a git reset --hard HEAD. The file still doesn't contain
the changes. I have even tried checking out a different branch in the
build repo and then re-checking out the master that should have those
changes. Still nothing.
What's the proper technique for making sure you see the actual changes
that were pushed to a repo?
This is debian lenny with git version 1.5.6.5.
TIA,
-Harry
From: Harry Johnson <hidden> Date: 2016-06-15 22:50:26
Thanks! It was in that faq. So it sounds like I just need to do a git
reset --hard before doing the builds... This shouldn't be a problem
since that working tree should never have any local changes. It is
just a snapshot to be used for builds. However, it does sound like
maybe I should look into a bare repo and then the build repo could
just be a clone of that.
Thanks again!
-Harry
On Wed, Jan 19, 2011 at 5:50 PM, Sverre Rabbelier [off-list ref] wrote:
Heya,
On Wed, Jan 19, 2011 at 23:30, Harry Johnson [off-list ref] wrote:
quoted
What's the proper technique for making sure you see the actual changes
that were pushed to a repo?
From: Alex Budovski <hidden> Date: 2016-06-15 22:50:26
On Thu, Jan 20, 2011 at 10:10 AM, Harry Johnson [off-list ref] wrote:
Thanks! It was in that faq. So it sounds like I just need to do a git
reset --hard before doing the builds... This shouldn't be a problem
since that working tree should never have any local changes. It is
just a snapshot to be used for builds. However, it does sound like
maybe I should look into a bare repo and then the build repo could
just be a clone of that.