Checkout after adding a project

To me the workflow after adding a project that has already a history is not clear.

Here’s what I did:

$ meta project add js-multihash [e-mail]:multiformats/js-multihash.git
meta project adding '[e-mail]:multiformats/js-multihash.git' at js-multihash
created /home/vmx/src/pl/meta/ipld/js-multihash
Initialized empty Git repository in /home/vmx/src/pl/meta/ipld/js-multihash/.git/
set remote origin to [e-mail]:multiformats/js-multihash.git
adding "js-multihash": "[e-mail]:multiformats/js-multihash.git" to .meta file at /home/vmx/src/pl/meta/ipld/.meta
adding js-multihash to .gitignore at /home/vmx/src/pl/meta/ipld/.gitignore

js-multihash isn’t checked out yet:

$ ls -a js-multihash
.  ..  .git

So I though I do a meta git update:

$ meta git update
all repositories in .meta are cloned locally

That doesn’t do anything. Next try is a pull (that would also screw with your existing repos):

$ meta git pull 
…
here is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> master

A checkout would make more sense:

$ meta git checkout
js-multihash:
fatal: You are on a branch yet to be born
js-multihash: command 'git checkout ' exited with error: Error: Command failed: git checkout

There’s still no proper checkout.

Next is then just removing the directory and using update:

$ rm -Rf ./js-multihash
$ meta git update

*** the following repositories have been added to .meta but are not currently cloned locally:
*** { 'js-multihash': '[e-mail]:multiformats/js-multihash.git' }
*** type 'meta git update' to correct.


 cloning missing repositories


js-multihash:
Cloning into 'js-multihash'...
remote: Enumerating objects: 7196, done.
remote: Total 7196 (delta 0), reused 0 (delta 0), pack-reused 7196
Receiving objects: 100% (7196/7196), 6.11 MiB | 5.40 MiB/s, done.
Resolving deltas: 100% (1373/1373), done.
js-multihash

That does the actual checkout as I would expect it.

So it is expected that meta project add is about new projects and not existing ones.

[mateodelnorte]

I’m not against renaming the current add command to meta project init and creating a new meta project add which expects a remote to exist.

[nwillc]

It confused me that the meta git pull failed after the project add, but worked if I did a fresh meta clone of same repo elsewhere…