3279308836
/
LRR
forked from mrlan/LRR
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Merge pull request #4 from lanlab-org/Hui-improve-README.md 

Hui improved README.md
SIMPLICITY_Bug-189_Course_Delete_btn
Software Project Management 2020-03-22 20:58:46 +08:00 committed by GitHub
parent fbc819bffc 4546f6b0dd
commit 903eee2214
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -64,10 +64,15 @@ Send Hui (lanhui at zjnu.edu.cn) an email message including your GitHub account
Currently, there are 9 members in *Lan Laboratory* (https://github.com/orgs/lanlab-org/people). Currently, there are 9 members in *Lan Laboratory* (https://github.com/orgs/lanlab-org/people).
You will use the feature-branching workflow when interaction with the central repo. The main point of this workflow is that you work on a branch on your local drive, push that branch You will use the feature-branching workflow (see below) when
to the central repo, and create a Pull Request (i.e., Pull Me Request) at GitHub for other people to review your changes. interacting with the central repo. The main point of this workflow is
that you work on a branch on your local drive, push that branch to the
central repo, and create a Pull Request (i.e., Pull Me Request) at
GitHub for other people to review your changes. When everything is
OK, then you could merge your changes to the master branch in the
central repo.
I believe that *code review* is a very important activity for effectively improving code quality and promoting participation. I believe that *code review* at the Pull Request stage is a very important activity for effectively improving both code quality and team quality.
## The feature-branching workflow ## The feature-branching workflow