Question

I am setting up a remote repo that needs to house both a staging version of my code and a production version of the code (each branch will be deployed to their designated servers for testing / production).

I would like to only allow changes to be pushed from local machines to the remote staging branch, and then when we have decided that the staging branch is good to go, we could merge the staging branch into the production branch, and then deploy from there.

Basically, something like:

1. local.branch -> remote.staging
2. test on staging server
3. remote.staging -> remote.production
4. deploy remote.production

Is it possible to manage remote repos in this way? If so how?

Also, is there a better way to do this?

Answer 1

I believe that the (a) normal/supported workflow would be

1. local(staging).branch -> remote.staging
2. test on staging server
3. local(staging).branch -> local(production).branch
4. local(production).branch -> remote.production
5. deploy remote.production

Is that a scenario not possible for you?