On Tue, Dec 11, 2012 at 2:37 PM, Paul T. Bauman <ptbau...@gmail.com> wrote: > On Tue, Dec 11, 2012 at 3:21 PM, John Peterson > <peter...@cfdlab.ae.utexas.edu> wrote: >> > > As a git noob - thanks very much. I think this will be very helpful for me. > > How does this workflow interact with "pull requests" (if at all)? I was > wondering if it might be a good idea to have the commits to the libMesh > master go through a pull request and have one of the "core" developers have > a look before it gets committed (even if the committer is another > developer). TIA,
So, as I understand it, a pull request would come from someone else (Joe, say) who has a github account but does not have write access to the libmesh repo. It would be in the form of a URL and a branch name to pull. When you receive the request, you could (haven't tried this) git co -b joes_branch git pull joes_url joes_branch At this point you are ready to do the steps 1-9 previously mentioned to incorporate Joe's branch into a linear history and push it into the repo if all is well. We are testing this now, and I'll let you know more details. -- John ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
