Git Development-Test-Production branches proccess [closed]

问题

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 10 months ago.

Improve this question

I am interesting in this process:

First I'd like to make any in my development branch, than it should be pushed to Test (master) branch and, therefore, to production.

For me the process:

1. init commit
   then, make prod branch from master init commit
   then, make dev branch from master init commit

2. checkout to dev branch
   then, do any
   then, commit
   then, checkout to master
   then, merge with dev

3. Do tests
   then, commit
   then, checkout to prod
   then, merge with master
   

Is this a right way to use this way or not? If not, explain please the right process.

Thanks a lot

回答1:

You are looking for something similar to the git flow workflow.
Read all about it in the following post by Vincent Driessen

回答2:

That would well if you don't have may feature to develop in parallel.

If you do and said features needs to be integrated, then the gitworkflow (one word) is a better fit.

The main advantage is that you can merge multiple feature branch, and then decide to remove some of them (because they are still too buggy, not ready)

来源：https://stackoverflow.com/questions/37469810/git-development-test-production-branches-proccess