Re: Renaming the repositories' primary branches

My list was incomplete: I have also updated the did-imp-guide repository.

Ivan

> On 25 Mar 2021, at 11:16, Ivan Herman <ivan@w3.org> wrote:
> 
> All done.
> 
> If you have a local clone, github's advice is to issue the following commands:
> 
> 
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
> 
> 
> Based on the feedback of github I think that PR-s that have been issued from a forked repository have also been automatically redirected to 'main', so if you have such a PR you should be all right. The gh-pages features (ie, the w3c.github.io <http://w3c.github.io/> URL-s) all seem to work, too.
> 
> Please shout if you experience any problem, one of us (possibly the more seasoned Git(hub) users like Amy or Manu if I do not know the answer) will help you out!
> 
> Cheers
> 
> Ivan
> 
> P.S.1. If you use one of the apps for github (like GitRaken or Sourcetree), it is probably a good idea to re-start those to force them to re-read the local configuration of the repo.
> 
> P.S.2 If you experience a problem with your local clone, remember that git has the wonderful equivalent to a machine reboot: you wipe out your local clone and make a new one... I have to admit that I did find myself in a git(hub) drama time-to-time (including with one of these 'master'->'main' renames) when that was the quickest way of settling everything right instead of trying to understand what the heck had happened :-)
> 
> 
>> On 24 Mar 2021, at 09:05, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
>> 
>> Now that the CR publication is behind us, I propose to go ahead and rename the primary branches from 'master' to 'main' for the following repositories:
>> 
>> did-spec-registries
>> did-use-cases
>> did-rubric
>> did-test-suite
>> 
>> I propose to do this tomorrow, 25th of March.
>> 
>> In my experience with other repositories the transfer goes mostly smoothly. When done, I will circulate the set of git commands that you will have to issue in your local clones (if you have any), although those commands are also shown in a github popup the first time you go to that repository with your login. If you have active PR-s from a clone, those are automatically re-assigned by github, you do not have anything to do. I am not sure whether that is also true if you have a PR from a forked repository (as opposed to a clone of the core repository itself), better check.
>> 
>> There is one hiccup that I have experienced several times: the gh-pages feature, ie, to look at the editor's draft served from github, often goes wrong and you get a 404. I have my tricks now on how to settle that, and I hope it will work out this time, too, but if you experience a problem you will have to shout at me… (In any case, a reload in your browser bypassing the browser cache is always a good idea…)
>> 
>> Cheers
>> 
>> Ivan
>> 
>> ----
>> Ivan Herman, W3C 
>> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
>> mobile: +33 6 52 46 00 43
>> ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>
>> 
> 
> 
> ----
> Ivan Herman, W3C 
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +33 6 52 46 00 43
> ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>
> 


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43
ORCID ID: https://orcid.org/0000-0003-0782-2704