Shulou(Shulou.com)06/02 Report--

This article mainly introduces the process analysis of the three working methods in Git, which has a certain reference value, and interested friends can refer to it. I hope you will gain a lot after reading this article.

There are three ways to use Git in the process of project development, which are centralized workflow, Git Flow workflow and Forking workflow. The following mainly focuses on the Git workflow.

Centralized workflow (rarely used)

A centralized workflow, like SVN, uses a central repository as a single point entity for all modifications to the project. All changes are committed to the Master branch. The main difference between this approach and SVN is that developers have native libraries, but many features of Git are not used.

Forking workflows (occasionally used)

Forking workflow is based on GitFlow and makes full use of the functions of Fork and pull request of Git to achieve the purpose of code review. It is more suitable for developers who manage large teams safely and reliably, and can accept submissions from untrusted contributors. (mainly to review the code of members outside the team, Linux's virtual team uses more).

Occasionally, if there is a need for non-team members to help us solve the problem, we may use it.

GitFlow Workflow (most popular)

Gitflow workflow sets up independent branches for function development, release preparation and maintenance, which makes the release iterative process more smooth and makes full use of the characteristics of the branches. The strict branching model also provides some very necessary structures for large projects. The following figure is a complete diagram of the development method, but the actual development may be more concise:

Git Workflow Demo

Demo instructions:

Create a branch in Eclipse and name it the featureA branch:

The novice completes the A function in the featureA branch, and then submits it to the local library:

Then push to the remote library:

Next, the veteran programmer pulls the project:

After pulling and switching from the master branch to the FeatureA branch, you can see the changes made by the novice:

Next, merge the FeatureA branch and the master branch locally, and then submit them to the remote library:

First switch to master branch → for merge and → push to remote database

Thank you for reading this article carefully. I hope the article "process Analysis of three working modes in Git" shared by the editor will be helpful to you. At the same time, I also hope that you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.