Deploying with an empty repositoryUrl (i.e. without pulling from git) doesn't seem to work

Hi,

The documentation says that by leaving repositoryUrl empty (though that’s a bit ambiguous) shipit can be used to deploy without fetching from git (possibly using the local directory?): “If empty Shipit will try to deploy without pulling the changes.”

Now when I try to do that, it seems to ignore the above and tries to do the normal flow, it seems, which fail because of the missing repo url:

Running 'deploy:init' task...
Finished 'deploy:init' after 647 μs

Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/tmp/tmp-100255o9Se5wCMUtf"
Initialize local repository in "/tmp/tmp-100255o9Se5wCMUtf"
Running "git init" on local.
@ Initialized empty Git repository in /tmp/tmp-100255o9Se5wCMUtf/.git/
Repository initialized.
List local remotes.
Running "git remote" on local.
Update remote "" to local repository "/tmp/tmp-100255o9Se5wCMUtf"
Running "git remote add shipit " on local.
@ usage: git remote add [<options>] <name> <url>
@
@     -f, --fetch           fetch the remote branches
@     --tags                import all tags and associated objects when fetching
@                           or do not fetch any tag at all (--no-tags)
@     -t, --track <branch>  branch(es) to track
@     -m, --master <branch>
@                           master branch
@     --mirror[=<push|fetch>]
@                           set up remote as a mirror to push to or fetch from
@
'deploy:fetch' errored after 27 ms
Error: Command failed: git remote add shipit
usage: git remote add [<options>] <name> <url>

    -f, --fetch           fetch the remote branches
    --tags                import all tags and associated objects when fetching
                          or do not fetch any tag at all (--no-tags)
    -t, --track <branch>  branch(es) to track
    -m, --master <branch>
                          master branch
    --mirror[=<push|fetch>]
                          set up remote as a mirror to push to or fetch from


    at ChildProcess.exithandler (child_process.js:270:12)
    at emitTwo (events.js:125:13)
    at ChildProcess.emit (events.js:213:7)
    at maybeClose (internal/child_process.js:921:16)
    at Socket.stream.socket.on (internal/child_process.js:348:11)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at Pipe._handle.close [as _onclose] (net.js:549:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[EduardsE]

How would one deal with a monorepo and microservices where all your services are in one git repo, but you would like to deploy them separately?

[sandervankasteel]

I have found a workaround for this (if this is still relevant for you @atleta )… Install shipit-utils add the following snippet to your shipitfile.js

  var utils = require('shipit-utils');

  // Deploy from working directory without repository fetch
  utils.registerTask(shipit, 'deploy:fetch', function() {

    // Set the workspace variable which is originally set in overridden deploy:fetch
    // This variable is needed in deploy:update and some other tasks
    shipit.workspace = shipit.config.workspace;
  
    shipit.emit('fetched');
  });

And of course set your repositoryUrl to an empty string 😃