On Sat, Sep 15, 2012 at 7:41 AM, Alex Harvey <[email protected]> wrote:
> Hi Andy, if you are still there I have another question - I would now like > to move on to work on another bug but GitHub apparently doesn't easily let > you fork multiple copies of the same repository. It will, but you shouldn't need to - with git, you generally work in a topic branch created from the branch you want to base your changes on. There is a good explanation here: https://github.com/dchelimsky/rspec/wiki/Topic-Branches The key difference between our workflow and his is that we use GitHub pull requests rather than patches when the changes come back. So, where he has "git format-patch", we would have you push to your own repository, then use GitHub to send a pull request. We have some more documentation on the whole process over at https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
