New option: remote

[jugglinmike]

I'd like to push to a repository that is not my "origin" remote. This plugin exposes an option named "repo" that allows me to specify any URL, but I would like to limit duplication by instead specifying the remote's name (which I have already registered within the repository).

The discussion in gh-15 includes references to a "remote" option. This sounds like it might be relevant, but there is currently no documentation for it.

[tschaub]

The option is still there, but the docs were causing confusion. See f749b7c97611ed0c201ef4d50e52e2d221b2c1b4. If you can use clone and remote to do what you want, I'd accept a pull request that brought back the documentation.

[jugglinmike]

Since the remote option relies on the clone option, and the clone option is intended to be a full git URL, I think the current implementation is incompatible with my goal (to avoid duplicating configuration data). If this is true, it would take a backwards-breaking API change to address.

[tschaub]

The clone option is a path to an existing clone. The repo option is the URL for a remote repository.

You should never use the remote option together with clone. But I'm pretty sure that using remote together with clone is what you are looking for.

Yes, the short option names are confusing.

[jugglinmike]

Here's my understanding: The newly-cloned repository created by the plugin will not be have the configuration of the repository I am using directly. So even though when I run

$ git remote add upstream git://some-url.git

...I can verify with

$ git config --get remote.upstream.url

...this information will not be available from the new "clone" repository created by this Grunt task.