[Scilab-Dev] git push on forges

[Clément David]

Hello Samuel,

`git push origin master` will push your local branch master to the matching remote branch ; to be
more explicit you could also use `git push origin master:master`.

If this command still fail, could you send us the .git/config file from the scidoe directory ? It is
also possible that behind a strict firewall the ssh port are closed (the codereview use an explicit
non ssh port), could you try from home (or through mobile phone tethering) ?

Thanks,

--
Clément

Le dimanche 22 juillet 2018 à 16:38 +0200, Samuel Gougeon a écrit :
> Hello,
> After having released the module scidoe 0.4.1, i am trying to update with git the source files of
> scidoe on its forge.
> It's the first time that i use the forge as administrator of a project.
> cloning the project with git is OK
> updating local files according to the 0.4.1 version is OK
> committing the list of changed files is OK, with
> git add *
> git status                                             => ok, i get the right green list
> git commit -m "version 0.4.1"
> But then, the commit must be pushed. The page https://forge.scilab.org/index.php/p/scidoe/source/h
> elp/ indicates the command
> $ git push origin master
> After validation, i always get.. nothing: the git session is just waiting... without error, and
> without doing anything.
> I have well set my public key on my forges profile (it starts with ssh-rsa and ends with Mylogin at m
> y-computer-name). I did not do anything else on my git, since i use the same key as for the Scilab
> CodeReview.
> 
> What's wrong or missing in this protocol?
> 
> Any help would be appreciated, here or in private.
> 
> Thanks in advance.
> Samuel
> 
>  _______________________________________________
> dev mailing list
> dev at lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/dev