Allow specifying the remote to push to about grunt-release

[geddski]

if grunt-release were a multitask problem solved... the arrays of options
thing tends to really complicate the code. Maybe we should just make it a
multitask already.

On Wed, Feb 19, 2014 at 7:46 PM, Patrick Connolly
[email protected]:

We're planning to use grunt-release to sign and push releases to heroku
and then github if that succeeds.

It would be great to set the remote to push to. Even better, it would be
great to specify an array of remotes to push to in succession.

Would this be a PR that you'd consider accepting?

Reply to this email directly or view it on GitHubhttps://github.com//issues/67
.

[patcon]

Sorry man, but I'm unsure whether you are in favour of multiple remotes or not. Either single or multiple is a step forward, so I'm happy either way.

You mentioned "array of options", and just to clarify, this was all I meant by multiple remote support:

  release: {
    options: {
      pushRemotes: ["origin", "heroku"],
      bump: false, //default: true
      file: 'component.json', //default: package.json
      ...

The idea was that then grunt-release could run git push <remote> rather than just git push :)

[jasonkarns]

dupe of #41

[patcon]

Good point! Thx