On Wed, 11 Sep 2019, Jed Brown via petsc-dev wrote: > Please fork the repository on GitLab > (https://gitlab.com/petsc/petsc/-/forks/new) and push your branch to the > fork, then make a merge request. If you become a regular contributor, > we can give you push privileges to the main repository. > > Pierre Gosselet via petsc-dev <petsc-dev@mcs.anl.gov> writes: > > > Dear all, > > I am sorry, I have not understood how to migrate Push Request from > > bitbucket to gitlab. > > > > I think I need the equivalent of > > git remote set-url origin https://gitlab.com/petsc/petsc.git > > applied to my development branch (I see that my branch's remote is > > incorrect in .git/config). > > You can fix that using git branch --set-upstream-to (see the man page).
BTW: I normally do 'git fetch -p' - this updates all remote references [and deletes origin/* references that don't exist on the remote repo]. And then I can push any local branches that I need - similar to a newly created branch. i.e git push -u origin branch-name Satish > > > Or am I supposed to make a fresh fork and MR from gitlab ? > > > > thank you for your help. > > best regards > > pierre > > > > > > > > -- > > Pierre Gosselet > > CR CNRS (research agent) > > LMT -- ENS Paris-Saclay/UMR8535 > > 61 av. du président Wilson, 94235 CACHAN > > tel: +33 1 47405333 >