Hi,
Yes, that's almost correct, and the only possible confusion was my own
fault from my previous email to David.
The 'git remote -v' gives which remote repositories we are linked to. Since
David will rename cf-conventions to conventions, we need to update our
local repository (personal computer) to look for the remote in the right
place.
So first we check what we have with the 'git remote -v', and we should have:
git at github.com:cf-convention/cf-conventions.git
or
https://github.com/cf-convention/cf-conventions.git
depending on the protocol that is used. The first one for SSH, and the
second one for HTTPS.
One possible outcome is:
origin git at github.com:cf-convention/cf-conventions.git (fetch)
origin git at github.com:cf-convention/cf-conventions.git (push)
which means that the official repository is linked using SSH and is named
(alias) origin. For this case, the update would be
git remote set-url origin git at github.com:cf-convention/conventions.git
if the protocol was HTTPS, it would be:
git remote set-url origin
https://github.com/cf-convention/conventions.git
And one can check the changes by running again the 'git remote -v'.
On my case, since I forked the official repository and use SSH, I get:
origin git at github.com:castelao/cf-conventions.git (fetch)
origin git at github.com:castelao/cf-conventions.git (push)
upstream git at github.com:cf-convention/cf-conventions.git (fetch)
upstream git at github.com:cf-convention/cf-conventions.git (push)
which means that I would need to update not the upstream instead of origin.
Origin is pointing to my fork in my account area in github, which I don't
need to change. Thus for my case I would run
git remote set-url upstream git at github.com:cf-convention/conventions.git
and my origin could keep the same, but my local repository would know how
to find the upstream to keep my fork updated with the official repository.
I hope that it helps. Let me know the questions,
Gui
On Fri, Jul 5, 2019 at 9:00 AM David Hassell <david.hassell at ncas.ac.uk>
wrote:
> Hello,
>
> Many apologies, but this week caught up with me, and I didn't get round to
> changing the repository names. But I *will* do it on Monday 8th July.
>
>
> If you need to update a local repository, Guilherme pointed out that it
> might be a good idea to double check what you have before update the
> origin, with
>
> $ git remote -v
>
> For example, if you have a fork of cf-conventions called 'origin',
> then the above command might return ...
>
> origin git at github.com:castelao/cf-conventions.git (fetch)
> origin git at github.com:castelao/cf-conventions.git (push)
> upstream git at github.com:cf-convention/cf-conventions.git (fetch)
> upstream git at github.com:cf-convention/cf-conventions.git (push)
>
> ... and you wouldn't update 'origin; rather you would update 'upstream' in
> this case:
>
> $ git remote set-url upstream https://github.com/cf
> -convention/conventions.git
>
> (I hope that I have got this right, Guilherme!)
>
> All the best,
> David
>
> On Wed, 26 Jun 2019 at 18:25, David Hassell <david.hassell at ncas.ac.uk>
> wrote:
>
>> Hello,
>>
>> Somewhat later than I had intended, and following on from Jonathan's
>> well-received suggestions on this list (starting from 2019-03-22), I shall
>> be renaming the following CF GitHub repositories:
>>
>> https://github.com/cf-convention/cf-conventions will become: *https://github.com/cf-convention/conventions
>> <https://github.com/cf-convention/conventions>*
>>
>> https://github.com/cf-convention/cf-convention.github.io will become: *https://github.com/cf-convention/website
>> <https://github.com/cf-convention/website>*
>>
>> I shall do this on Tuesday 2nd July (following the principle of never
>> making changes that could affect other people just before the weekend).
>>
>> Aside from needing to rename our browser bookmarks, this should have no
>> adverse effects on most people.
>>
>> However, if you have cloned either of these repositories, the old names
>> should still work (according to
>> https://help.github.com/en/articles/renaming-a-repository), but it is
>> best to rename the remote URL as follows, e.g. for the "conventions" site:
>>
>> > git remote set-url origin
>> https://github.com/cf-convention/conventions.git
>>
>> (Don't take my word for it! See
>> https://help.github.com/en/articles/changing-a-remotes-url for more
>> details, for example.)
>>
>> Please let us know about any concerns that may still remain on this
>> topic, all the best,
>>
>> David
>>
>> --
>> David Hassell
>> National Centre for Atmospheric Science
>> Department of Meteorology, University of Reading,
>> Earley Gate, PO Box 243, Reading RG6 6BB
>> Tel: +44 118 3785183
>> http://www.met.reading.ac.uk/
>>
>
>
> --
> David Hassell
> National Centre for Atmospheric Science
> Department of Meteorology, University of Reading,
> Earley Gate, PO Box 243, Reading RG6 6BB
> Tel: +44 118 3785183
> http://www.met.reading.ac.uk/
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20190705/47b2d94a/attachment-0001.html>
Received on Fri Jul 05 2019 - 10:24:37 BST
