All work should better be under branch then merge.

[hyperchi]

@Jelly-Yu @qiuzhihui
Jelly keeps a great merging branch habit .
Seems like a better idea, since now we have a little more code to maintain.. avoid unnecessary push.
When git commit we can specify which file to commit.. instead of just commit the whole repo. Base on what I found on @qiuzhihui commit history, it seems like you are mostly committing the whole repo.
I will stick to this habit as well, if later on I have time to write code for it.
I'm not familiar with git. But should be sth like following.
@Jelly-Yu if not correct plz comment as well.

create xxx

git branch xxx

switch to xxx

git checkout xxx

commit to local

git commit -m ""

merge

git checkout master
git merge xxx

[qiuzhihui]

Ok. I'll do branch next time... wuwuwu

On Sat, Feb 27, 2016 at 2:57 PM, hyperchi notifications@github.com wrote:

@Jelly-Yu https://github.com/Jelly-Yu @qiuzhihui
https://github.com/qiuzhihui

Jelly keeps a great merging branch habit .
Seems like a better idea, since now we have a little more code to
maintain.. avoid unnecessary push.
When git commit we can specify which file to commit.. instead of just
commit the whole repo. Base on what I found on @qiuzhihui
https://github.com/qiuzhihui commit history, it seems like you are
mostly committing the whole repo.
I will stick to this habit as well, if later on I have time to write code
for it.
I'm not familiar with git. But should be sth like following.
@Jelly-Yu https://github.com/Jelly-Yu if not correct plz comment as
well.
create xxx

git branch xxx
switch to xxx

git checkout xxx
commit to local

git commit -m ""
merge

git checkout master
git merge xxx

—
Reply to this email directly or view it on GitHub
#7.

[hyperchi]

@qiuzhihui @Jelly-Yu
Say you have a problem wanna solve open a ticket for it. Then in commit info
Say you open a issue
number 20 "ssssss"
commit -m "ticket_20 ssss" file1.py file2.py

So that we can back track what problem you solved in git log.

[Jelly-Yu]

got it.