Helabs/jumpup-heroku — pull request #37 by TiuTalk (2014-02-24 19:02:11+00:00)
Title: Create Heroku remotes with the app name

Currently, every time you deploy to staging or production, **jumpup-heroku** will check if there is a remote called "heroku", if there is none, it will create one called "heroku".

The problem here, as reported in #35 is that after you deploy to production, the remote will still be set to the production app, and if you run any heroku command (like `heroku run console`) you might end on the wrong environment.

With the changes proposed on this PR, it will create a remote based on the app you're deploying to.. So if you deploy to app `helloworld-staging` (staging) it will create a remote called `helloworld-staging`, and when you deploy to app `helloworld` (production) it will create a remote called `helloworld`.. You will end with two remotes.

After this, if you run `heroku run console`, it will force you to provide an app name via the `--app` or the `--remote` param, making sure you're accessing the right app.

Fix #35