[racket-dev] pushing to new repos

Sorry I am late to the party but how do I push to the new repos: 

I tried 

** Asumu's method: 


> [:~/Hub/Hub] matthias% hub remote add -p racket/htdp
> [:~/Hub/Hub] matthias% git push
> error: The requested URL returned error: 403 while accessing https://github.com/github/hub.git/info/refs
> 
> fatal: HTTP request failed



** Sam's method: 


> [:~/Hub/Hub] matthias% hub remote add -p racket/htdp
> [:~/Hub/Hub] matthias% git push
> error: The requested URL returned error: 403 while accessing https://github.com/github/hub.git/info/refs
> 
> fatal: HTTP request failed

** and a plain push: 

> [:htdp/htdp-lib/2htdp] matthias% git push
> fatal: remote error: 
>   You can't push to git://github.com/racket/htdp.git
>   Use https://github.com/racket/htdp.git


To no avail. Hints appreciated -- Matthias



Sam wrote a long time ago: 

> I think this is the case for everyone.
> 
> I've used the `hub` [1] tool to address this. Once I have a checkout,
> if I need to push, I do:
> 
>    $ hub remote add -p racket/typed-racket
> 
> and then
> 
>    $ git push racket
> 
> Having an option to `raco pkg update` and `raco pkg install` to use
> the corresponding ssh URL for `--clone` would be nice, though, and I
> think it should be pretty easy to add. :)
> 
> Sam
> 
> On Tue, Dec 16, 2014 at 4:42 PM, Asumu Takikawa <asumu at ccs.neu.edu> wrote:
> Hi all,
> 
> I've been trying to adjust to the new package-split workflow now and
> I've bumped into a small usability problem and I wanted to see if anyone
> else has encountered this or if my config is just broken somehow.
> 
> On a fresh build of Racket, if I do the following:
>  raco pkg update --clone typed-racket
> 
> it will install TR from github and reinstall. An excerpt from the config
> for that git repo looks like this:
> 
>  [remote "origin"]
>          url = git://github.com/racket/typed-racket/
> 
> The problem is that this URL is not as useful as it could be because
> github won't let you push to it (at least I can't seem to). The
> corresponding SSH URL "git at github.com:racket/typed-racket.git" lets me
> push.
> 
> Is this something other people have encountered or is there some git
> config that I should fix on my end?
> 
> FWIW, I have just been doing "git remote set-url origin <url from github error message>" and it has worked well and been easy. 
>