# Git remote branches for deployment **URL:** \ **Category:** Deployment\ **Created:** [August 7, 2008, 5:19pm UTC](https://www.ruby-forum.com/t/git-remote-branches-for-deployment/145296 "2008-08-07T17:19:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![robby247365](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/9d8465/32.png) [@robby247365](https://www.ruby-forum.com/u/robby247365)\ **Post date:** [August 7, 2008, 5:19pm UTC](https://www.ruby-forum.com/t/git-remote-branches-for-deployment/145296/1 "2008-08-07T17:19:25Z")
Hey there, This is possibly a better question for the Git community, but thought that I’d ask here first. I’m having a little trouble figuring out a sane way of managing remote branches for deployment. Mainly due to just a lot of confusion about how to do it. We have a few environments for deployment (sandbox, staging, and production) and am not sure how to best manage two remote branches for deployment (and keep it easy for our team to work on both of those branches). With SVN, we were just switching over to the various _remote_ branches as necessary, but I really don’t find this to be as straight forward with Git. I saw this on Github ( [A Git deployment workflow - The GitHub Blog](http://github.com/blog/132-a-git-deployment-workflow) ) and at first it looks like it might do the trick, but someone who referenced that to me said they didn’t advise it because it wouldn’t retain history properly (not really sure what he meant). Any advice as I dive further into this? Thanks! Robby – Robby R. Chief Evangelist, Partner PLANET ARGON, LLC design // development // hosting > **[Planet Argon](https://www.planetargon.com/)** > > Planet Argon is a Ruby on Rails development agency specializing in maintenance and support for existing Rails apps. Based in Portland, OR, Planet Argon has been a member of the Rails community since 2004. [http://www.robbyonrails.com/](http://www.robbyonrails.com/) aim: planetargon +1 503 445 2457 +1 877 55 ARGON [toll free] +1 815 642 4068 [fax]