"Git" GitHub for Windows uses (3) GitHub flow usage

In chapter three, there is a pull request on GitHub, which shows all of this project or resource pulling requests.

This development process is based on GitHub flow's development model.

Online about GitHub Flow Simple introduction There are a lot, but I went to see a lap and a circle, Leng did not understand what this is really a thing. Just seeing GitHub flow related articles always go back and forth in the pull request feature.

He then went over the pull request and returned to the head to write the beginning of the article. At this point, we finally figured out

It turns out that GitHub flow is actually a development model, a way of thinking, and after Git manages the project, it's a way of managing the new branches that are being submitted by the individual users around the project.

This management idea is a flowchart that the GitHub flow website can describe.

--------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------

This project submission management process has the following steps:

"1. Create a branch

"2. Add a Submission

"3. Open Pull Request

4. Comment and review your code

"5. Deployment

"6. Merger

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------

Schematic diagram:

1. Create a branch

2. Add a Submission

3. Open Pull Request

4. Comment and review your code

5. Deployment

6. Merging

--------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------

Actual operation Flow "":

1. Procedure for creating a branch

1.1 Enter the client and then go to the GitHub website from the client

1.2 On the site you can see that the pull request shows that there are 0 pulling requests

After 1.3, if you want to create a new pull request, you need to create a new branch or other merge, otherwise there is no way to create a pull request.

1.4 Then return the client, create a new branch on the client, make a file modification, and commit the branch

1.5 Push new branch related changes to GitHub

This one-step operation simulates every project involved in this, new user, opens a new branch locally, makes the relevant changes and pushes the new local branch onto GitHub

1.6 Then in the Repository option, click View on GitHub to go to the GitHub website

2. Add a Submission

2.1 You can see that you can create a new pull request at this time

2.2 Select the package base branch and the branch to be compared

2.3 Create a pull request

3. Open Pull Request

4. Comment and Review the Code

Also I can close or reopen the commit

Return to see a pull requst here

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ----

For deployment and consolidation, take action later when you actually deploy the project.

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ----

End!

Reference: Http://youngxhui.github.io/2016/05/15/GitHub-for-windows%E4%BD%BF%E7%94%A8%E6%95%99%E7%A8%8B%EF%BC%88%E4%B8 %89%ef%bc%89/

"Git" GitHub for Windows uses (3) GitHub flow usage