Re: [Editors] Upcoming Editor's call

To push you have to use the SSH URL when setting up your clone.  That requires 
correctly setting up an SSH key with GitHub and having it available when you 
clone and push.   I did not have this last set up correctly.


peter



On 2/8/23 14:55, Peter F. Patel-Schneider wrote:
>
> When I used the https variant I could read but not push back because GitHub 
> complained that password login was not allowed.
>
> Can someone please describe how to clone one of the repositories in a way 
> that allows us to push back to a branch on it.
>
>
> peter
>
>
>
> On 2/8/23 14:05, Gregg Kellogg wrote:
>>> On Feb 8, 2023, at 10:27 AM, Peter F. Patel-Schneider<pfpschneider@gmail.com>  wrote:
>>>
>>> I just ran into the first problem in making a change to RDF semantics.
>>>
>>>
>>> To push to the repository I think I need to use the SSH URL so that I can use public key signon.  But I can't clone the repository using that HRL
>>>
>>>
>>> idefix ~> git clonegit@github.com:w3c/rdf-semantics.git
>>> Cloning into 'rdf-semantics'...
>>> git@github.com: Permission denied (publickey).
>>> fatal: Could not read from remote repository.
>>>
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>> idefix ~>
>>>
>>>
>>>
>>> What is the process that needs to be done to clone a repository and then be able to push back to a branch on it?
>> This probably varies with different clients. THe “Code” button on the upper right of the repo page should offer two alternatives:
>>
>> *git@github.com:w3c/rdf-semantics.git, and
>> *https://github.com/w3c/rdf-semantics.git
>>
>> My guess is that you need to use the “https” variant.
>>
>> Gregg
>>
>>> peter
>>>
>>>
>>>