The skale-cli from skale-me

skale-cli's People

Contributors

Stargazers

Watchers

skale-cli's Issues

Fail running `skale run`

I'm just kicking the tires on skale. I just did a fresh npm install of skale, and used it to create a new skale app. I moved into the directory, and skale run. I received this output:

markbradshaw@MacBook-Pro test_skale (master)$ skale run
fatal: ambiguous argument 'skale/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
child_process.js:508
    throw err;
    ^

Error: Command failed: git diff skale/master
fatal: ambiguous argument 'skale/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

    at checkExecSyncError (child_process.js:465:13)
    at Object.execSync (child_process.js:505:13)
    at run_remote (/Users/markbradshaw/.nvm/versions/node/v4.5.0/lib/node_modules/skale/skale.js:251:28)
    at Object.<anonymous> (/Users/markbradshaw/.nvm/versions/node/v4.5.0/lib/node_modules/skale/skale.js:89:5)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)

Judging from the code in skale/skale.js I'm guessing the cli is usually being run from a git checkout rather than global npm install, so perhaps this got missed. It's also probably not a good idea to assume the user has git installed.

skale deploy: handle git config if necessary

The first time git is used on a machine, it requests user identity. This should be handled transparently by the skale deploy command.
Thanks @philippe56 for the report

Recommend Projects