When all the features related to a new release are implemented in the develop branch it’s time to branch the code to the release branch where there you’ll start to test properly before the final deployment. When the feature will be ready and tested it could be rebased inside the develop branch, our goal is to have always a stable version of develop branch because we merge the code only when the new feature is completed and it’s working. When you clone a GIT repository in your local folder you have immediately to create a branch from the master called develop, this branch will be the main branch for the development and where all the developers in a team will work to implement new features or bug fixing before the release.Įvery time a developer needs to add a new feature he will create a new branch from develop that allow him to work properly in that feature without compromise the code for the other people in the team in the develop branch. Git flow works with different branches to manage easily each phase of the software development, it’s suggested to be used when your software has the concept of “release” because, as you can see in the scheme above, it’s not the best decision when you work in Continuous Delivery or Continuos Deployment environment where this concept is missing.Īnother good point of this flow is that fits perfectly when you work in team and one or more developers have to collaborate to the same feature.īut let’s take a look closer to this model. These 2 methods can really help you to manage your project and optimise your workflow in the team. The principals ways to manage a software in GIT are: the Git Flow and the Github Flow. I really read a lots of blog post to check different points of view and to find out which is the best technique to use in different situations. Recently I’ve spent time to study a good way to manage a software projects with GIT.
0 Comments
Leave a Reply. |