Geek asks and answers

Git - make development and wizard track various repositories. Reasonable?

I have a project that is in git and deployed to heroku. The remote URL git@heroku.com:myappname.git, and .git / config looks like this:

[core]
  repositoryformatversion = 0
  filemode = true
  bare = false
  logallrefupdates = true
[remote "origin"]
  fetch = +refs/heads/*:refs/remotes/origin/*
  url = git@heroku.com:myappname.git
[branch "master"]
  remote = origin
  merge = refs/heads/master

I just created a new heroku application called "myappname-staging" which I want to use as an intermediate site for this application. I thought that I would configure it so that the host branch pressed the production console, and the development branch pushed to the intermediate console. Is this a reasonable / common way to handle this situation?

I can’t figure out how to do this. When I made an intermediate application on the hero, he gave me this back:

Creating myappname-staging.... done
http://myappname-staging.heroku.com/ | git@heroku.com:myappname-staging.git
Git remote heroku added

And my configuration now looks like this:

[core]
  repositoryformatversion = 0
  filemode = true
  bare = false
  logallrefupdates = true
[remote "origin"]
  fetch = +refs/heads/*:refs/remotes/origin/*
  url = git@heroku.com:myappnamestef.git
[branch "master"]
  remote = origin
  merge = refs/heads/master
[remote "heroku"]
  url = git@heroku.com:myappname-staging.git
  fetch = +refs/heads/*:refs/remotes/heroku/*
[remote "staging"]
  url = git@heroku.com:myappname-staging.git
  fetch = +refs/heads/*:refs/remotes/staging/*

Can anyone set me straight?

thanks max

+3
1

:

[branch "development"]
  remote = staging
  merge = refs/heads/master

:

$ git config branch.development.remote staging
$ git config branch.development.merge refs/heads/master

development master .

+5

More articles:


All Articles