Alec Larson

In this error message for `indo link metro-core`... ``` error: Global package metro-core does not exist. Did you run indo link yet? ``` ...this part... ``` Did you run indo...

``` fatal: refusing to merge unrelated histories error: { Error: Closed with non-zero exit code: 128 ```

When the `indo` command is linking local packages, it should check each local symlink to see if any are broken. If so, fix them.

For example: ``` $ cd my-package && indo link warn: Package named "my-package" is already registered. Replace it? [Y/n] ```

https://github.com/f/omelette.git

When the `indo` command runs, check for `.gitmodules` and offer to convert them to indo.

When the `indo` command is run, ensure the root `.gitignore` contains every vendor glob.

By default, `indo clone` clones into the `vendor` directory, which should be ignored already. But when a non-ignored path is provided, add it to the root `.gitignore`

This issue is about `indo share` and what it adds to `repos` in `.indo.json` config. Currently, the local branch name is used, but it should actually be the remote branch...

If the `url` or `head` of a repo is changed, running `indo` should update the local clone if it exists already. If uncommitted changes exist in the local clone, abort...