From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: ANN: Awesome-Ada
Date: Thu, 06 Dec 2018 08:43:18 +0000
Organization: A noiseless patient Spider
Message-ID: <lyftvb11w9.fsf@pushface.org>
References: <9cc33ea4-0164-4568-9295-c051342aed23@googlegroups.com>
	<3790db70-0f76-4f33-8ded-642dfeae9ca3@googlegroups.com>
	<lytvjt1vun.fsf@pushface.org> <ln1s6vkv0z.fsf@kst-u.example.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader01.eternal-september.org;
 posting-host="23b9e73b380780c85a4dbb052203df2b";
	logging-data="20836"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/hbs+CnURDYs4+tSnhpCQw4k5OKjd7pu8="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (darwin)
Cancel-Lock: sha1:d6fvbGIqCqfYMYcpXyOkAh/pgdg=
	sha1:dM5KQE8zX1vV0JREW9nOQCQlDEI=
Xref: reader01.eternal-september.org comp.lang.ada:54973
Date: 2018-12-06T08:43:18+00:00
List-Id: <comp.lang.ada>

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]