From: Bill D. <dr...@dm...> - 2012-11-09 00:12:13
|
On Thu, Nov 8, 2012 at 2:51 PM, Lieven Hollevoet <li...@li...> wrote: > Op 8-nov.-2012, om 17:18 heeft Bill Dripps <dr...@dm...> het volgende > geschreven: > > > I can contribute as a tester, but not as a developer. I am running the > latest svn trunk, not insteon. Here are my questions: > > > Welcome to test! > Thank you! > > What git command do I use to keep my github fork uptodate? > > If you only plan to test and not to provide code, check out the main > repository using this command > > git clone git://github.com/hollie/misterhouse.git Excellent! Just what I was looking for. I deleted my previous clone of my fork and did this instead. Worked great. > What git command do I use to keep my local repository up to date? > > git pull origin master > Again, works great. Of course it didn't pull anything this time, but I'm sure it will in the future. I am currently running this code and everything seems to be working just fine. > > How do I know when to grab a version to test? > > As it is now, people get notified of new pull requests because we agreed > that a notification would me made to the mailing list when a new pull > request is made. The pull request will typically be in the form of a branch > with a specific name. If you want to update your local working copy with the pull request to test > it out, then you do > > git checkout -b <branch_name> origin/<branch_name> > Great! I'll look for your notifications. Then test and report back to the list or to the pull request on the github > website. > Will do. So far the github code works just like the svn code as expected. Thanks, Bill |