Why use
git message should become a key issue of backtracking quickly locate the problem. If we do not submit written information or written information submitted bug fix, etc., when back problems are often confused.
Team practice guidelines
Principled commit code (particle size)
After the project code is stable, each submission must consider the size of the issue to try to make baby step
- No associated code can not commit the time
- Association code submission; if a lot of content can be internal stratification, followed by submission.
According to the current code module can handle the situation.
Must be submitted commit message
-
Did not commit message can not be submitted
-
Git commit -m is not increasing or the --message = parameter, two separate write information submitted.
Not recommended format:git commit -m 'Fix login bug'
Recommended use:
the Commit GitHub of the angular
rules reference:
http://www.ruanyifeng.com/blog/2016/01/commit_message_change_log.html
https://juejin.im/post/5c08c24a6fb9a04a0b21f754