[phobos] Push or pull?

[Don Clugston]

On 9 February 2011 09:33, Lars Tandle Kyllingstad <lars at kyllingen.net> wrote:
> On Tue, 2011-02-08 at 15:40 -0800, Sean Kelly wrote:
>> I still barely understand how Git works, but I'm starting to warm up to the workflow.  Using SVN, coordinating library and compiler changes (ie. spanning multiple repositories) generally resulted in a window where the library code was out of date or broken.  With Git I'm finding that I can create a series of pull requests that reference one another, which is a heck of a lot nicer than including multiple patch files to a bugzilla ticket.
>>
>> I'm still fuzzy on what to do if I want to create multiple pull requests that don't derive from one another though.  A fork for each one?  I'd hoped that I could create a branch for each, but haven't yet figured out how to push the branch upstream so I can generate the pull request from it.
>
> I've written a bit about that in the still-embryonic contributor's
> guide:
>
>    http://www.kyllingen.net/guide.html#publish
>
> It's probably a good idea to always create a new branch for each pull
> request, though, so I'll put a note about that in there, too.
>
> -Lars

I think github does you a major disservice by allowing you to do a
pull request on your master branch, without giving you a warning.