Wrongly claims child repos are not cloned locally

Ran git clone [e-mail]:<obfuscated>/dpo-meta-poc.git in the same directory (dpo/) as the child repos. That is the repos listed in .meta file:

*** the following repositories have been added to .meta but are not currently cloned locally:
*** { 'dpo-frontend': '[e-mail]:<obfuscated>/dpo-frontend.git',
  'dpo-account-frontend': '[e-mail]:<obfuscated>/dpo-account-frontend.git',
  'dpo-api-v2': '[e-mail]:<obfuscated>/dpo-api-v2.git',
  'dpo-api': '[e-mail]:<obfuscated>/dpo-api.git',
  'dpo-auth': '[e-mail]:<obfuscated>/dpo-auth.git',
  'dpo-manager': '[e-mail]:<obfuscated>/dpo-manager.git',
  'dpo-widget-api': '[e-mail]:<obfuscated>/dpo-widget-api.git',
  'dpo-environment': '[e-mail]:<obfuscated>/dpo-environment.git' }
*** type 'meta git update' to correct.

That is, the meta-directory/repo is a sibling to the listed directories/repos.

This causes the error:

dpo-meta-poc:
* master
dpo-meta-poc ✓

dpo-frontend:
dpo-frontend: command 'git branch ' exited with error: Error: spawnSync /bin/sh ENOENT
...

Anyway I can fix this?

[mateodelnorte]

If you use meta project add [name] [git location], you’ll see it adds a new item to .meta and .gitignore.

[mateodelnorte]

The point of meta is that it allows you to keep all of your separate repos in a structure that is easily able to be reproduced on other machines. As such, your meta repo has two jobs:

1. to denote the layout of your child repos
2. to keep files that don’t go in your child repos while ignoring the child repos so they’re not doubly tracked

Child repos go in .gitignore so that changes made to their files aren’t seen as changes in the meta repo. In the child repos, you just use git.