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: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.ada
Subject: Re: ANN: Awesome-Ada
Date: Wed, 05 Dec 2018 22:51:24 -0800
Organization: None to speak of
Message-ID: <ln1s6vkv0z.fsf@kst-u.example.com>
References: <9cc33ea4-0164-4568-9295-c051342aed23@googlegroups.com>
	<3790db70-0f76-4f33-8ded-642dfeae9ca3@googlegroups.com>
	<lytvjt1vun.fsf@pushface.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org;
 posting-host="c1f90fdc7f96d5c1497475e112934118";
	logging-data="12731"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX187a8wDQlkt6HrEK7SmJiLV"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:e1bgCryXCHJYvmI+EVHC/HjlLZI=
	sha1:eEbs0juK2i5yzAxq7INUquajV9c=
Xref: reader01.eternal-september.org comp.lang.ada:54972
Date: 2018-12-05T22:51:24-08:00
List-Id: <comp.lang.ada>

Simon Wright <simon@pushface.org> writes:
> Olivier Henley <olivier.henley@gmail.com> writes:
>> $ git clone https://github.com/ohenley/awesome-ada.git (you just
>> cloned the repo)
>
> $ cd awesome-ada (you are now in the cloned repo)
>
>> $ git checkout -b my-branch-to-edit-the-awesome-ada (you just created
>> a personalized branch)
>
> ------------------
>
> I'd support your suggestion to use Github. I used to be a
> Mercurial/Sourceforge person, but (a) Git is a lot more capable than Hg,
> even if there are some facilities that are too capable for mere mortals,
> and (b) Github itself is much more responsive and capable than SF.
>
> 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.

-- 
Keith Thompson (The_Other_Keith) kst@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"