Feature: Change repository origin

[PrzemekWirkus]

Description

I want to change origin or the Morpheus app repository, e.g. to my for of mbed-os.

Currently what I do is:

Create new application:

$ neo new appname
$ cd appname/mbed-os
$ git remote -v
origin  https://github.com/ARMmbed/mbed-os (fetch)
origin  https://github.com/ARMmbed/mbed-os (push)

Set new remote origin for my own mbed-os fork.

$ git remote set-url origin  https://github.com/PrzemekWirkus/mbed-os.git
$ git remote -v
origin  https://github.com/PrzemekWirkus/mbed-os.git (fetch)
origin  https://github.com/PrzemekWirkus/mbed-os.git (push)

And update

$ neo update

I want to work on my fork so I can later e.g. sent PR with new feature.

Is there a already a workflow for this type of action?

[0xc0170]

git or mercurial supports remotes (for hg it's paths). I think this could be useful addition (I have been doing remote set/change manually).

It could be mbed update --remote url sha/branch/rev ? this would change origin to the remote and pull it.

[bogdanm]

This is a good idea, but I'd extend it (or restrict it, depending on your view) to include the idea of "forks". Something like mbed fork <url>, mbed use-fork <url>. This could be quite handy for people that need to clone one or more of our repos.

[adbridge]

I would be in favour of the fork approach (having accidently pushed to master already). We should probably also write this into the workflow.

[screamerbg]

@PrzemekWirkus

I’m already using the following workflow with mbed CLI:

• Clone a repository, e.g. mbed import https://github.com/screamerbg/repo-origin. I’m leaving it as “origin” which is git’s default and mbed CLI’s preferred remote (in multiple remotes scenario)
• Associate the “origin” remote for push action with my fork, e.g. git remote set-url --push origin https://github.com/screamerbg/repo-fork
• Every time I commit and push, the commits are pushed against my fork. I can fetch from the original repo by mbed update or git pull, because that’s the associated fetch URL. If someone pushes to my fork, then I do explicit pull git pull https://github.com/screamerbg/repo-fork

Through the explained workflow above, mbed CLI keeps the reference to the original/origin repo (to which I’m intending to do a PR), and records hashes is against my local revision history, which is being pushed to my fork. Once the PR is accepted, all hash references become valid against the remote repo. Try it for yourself and let me know if that works for you.

[PrzemekWirkus]

@screamerbg OK, thanks. I will give it a try!

[screamerbg]

Workflow documented in the latest PR. https://github.com/ARMmbed/mbed-cli#forking-workflow