![]() At the end we have the release branch with tags that can help us to move between versions. If later we fix bugs in the master branch we need to cherry-pick them to the last release branch. The approach is good if we want to see each separate feature we just checkout in the branch what we need to look at.īut if we need to show our work we create a release branch with a tag as late as possible. And then the master branch pulls all changes from the production branch. A pre-production branch is the intermediate stage. When we have finished the feature, we deploy a production branch from the pre-production branch. I understand it this way: If we need to add a new feature we deploy a pre-production branch from the master branch. What relationships do they have between them? I've seen new terms like a pre-production, a production, a release (stable) branch and a staging environment, a pre-production environment, a production environment. This approach fits for extreme programming where the production branch is deployed several times in a day. ![]() And we (as developers) can create branches for adding new features or fixing bugs and merge them with production (master) branch. We have a master branch as a production branch. This approach works well if we seldom publish results of our work. If we have a critical bug in production, create new hotfix-branch, fix the bug and merge branch with production (master) and develop branches. If we have a bug in the release branch, fix it and pull changes into the develop branch. ![]() Sometimes we create a release branch to deploy our features in production. Also we have a develop branch where every developer merges his features. We've a master branch as a production branch. I've read the nice articles about it but I don't understand GitLab Flow very well. ![]() Recently I've found three concepts of a workflow in Git: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |