# Faster git deployment

DevFeed: [Faster git deployment](<https://devfeed.tech/articles/faster-git-deployment-38373.md>)

Original publisher: [Read original article](<https://meedamian.com/post/faster-git-deployment/>)

Author: hi@meedamian.com (Damian Mee)

Published: 2014-06-23T00:00:00Z

Content type: tutorial

Language: en

Sources: [Damian Mee | Blog | Portfolio | About](<https://devfeed.tech/sources/damian-mee-blog-portfolio-about.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [hosting](<https://devfeed.tech/topics/hosting.md>)

Tags: [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [git](<https://devfeed.tech/tags/git.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [how-to](<https://devfeed.tech/tags/how-to.md>)

## AI overview

A Git deployment technique configures a Heroku remote so one command pushes code to two repositories. The article notes that automatic deployment on every Git push may be risky for projects with many users and describes the approach as applicable to other Git repositories and cloud platforms that support Git deployment.

## Source excerpt

This trick let's you push to two repositories with one command. It is great for projects that need really rapid development and aren't yet populated by many users. Before using make sure that deploying with every git push will not result with catastrophic consequences. I assume Github for version control and Heroku for hosting, but it works with any remote Git repository and Cloud Platform offering deployment by git. First, repo needs to be created: