When examining the repos of other developers (especially when reviewing pull requests), I often:
(1) add their repo as a remote: git remote add foo [email protected]:foo/geotools.git (2) fetch commits, which does no merging: git fetch foo (3) checkout the commit of interest (a detached head): git checkout adc83b19e793491b1c6ea0fd8b46cd9f32e592fc No need to clutter my local repo with tracking branches. When I am done, I can just checkout something else. I can also merge or cherry-pick the commits I fetched. Kind regards, Ben. On 02/07/13 09:46, Landon Blake wrote: > I found out how to view the pull requests for the main GeoTools Git repo > on GitHub today. > > Is there a way to import this pull request from the GeoTools master to > my fork of the GeoTools master on GitHub? > > Should I then create a branch on my fork to integrate and examine the > changes in the pull request? > > Thanks for any tips. > > Landon -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
