Re: ANN: Awesome-Ada

[Simon Wright <simon@pushface.org>]

Keith Thompson <kst-u@mib.org> writes:

> Simon Wright <simon@pushface.org> writes:
>> Olivier Henley <olivier.henley@gmail.com> writes:
>>
>>> $ git checkout -b my-branch-to-edit-the-awesome-ada (you just created
>>> a personalized branch)
>>
>> I didn't know it was possible to let J. Random Hacker push a new
>> branch to your repo! I thought you had to fork on Github, push to
>> your own repo, & make the pull request from there. Agreed that this
>> is a workflow that you have to _really want_ to make work, until
>> you're used to it, when it seems like the way Nature intended. :-)
>
> In the example above, the user isn't pushing a branch to your repo.
> `git clone` creates a copy of your repo, and the user creates a new
> branch in that copy.  The user can then create a "pull request", which
> lets you propagate the new branch to your original repo, but only if
> you choose to accept it.  Nobody can modify your repo without your
> permission.

As I said, the workflow Oliver specified would only work if the user had
write permission in Oliver's repo. Of course you're right about the pull
request, but I can't create a pull request on Github that refers to a
commit on a branch in my cloned repo on my machine! It has to be from a
fork on Github.

[I could email you a pull request from my repo so long as the two repos
had a common ancestor and my repo was accessible to you, but to use
Github's mechanisms both repos need to be on Github]