3 ms·
You could, but you'd have to have some intermediate service to handle that process. One great choice is Travis CI[1] which is really a continuous integration se
by michaelmior 13y ago
You could, but you'd have to have some intermediate service to handle that process. One great choice is Travis CI[1] which is really a continuous integration service, but would let you do what you want. You can also just attach multiple URLs to a single git remote so you push to both GitHub and Heroku all the time.
However, I think running a test suite before deploying is a much safer option as it stops you from accidentally deploying something you haven't properly tested.
[1] http://docs.travis-ci.com/user/deployment/heroku/ http://docs.travis-ci.com/user/deployment/heroku/
- atmos 13y agoWe have a preview API in place for these types of deployment tasks. Lots of folks, travis/etc, seem to have piggy backed on top of successful builds too. http://developer.github.com/v3/repos/deployments/ http://developer.github.com/v3/repos/deployments/
- jon-wood 13y agoSeeing that in the list of events to listen to was probably the thing I was most excited to see, I'm looking forward to seeing where that API goes!
- nthj 13y agoCircleCI is another option: https://circleci.com https://circleci.com