Changes between Version 28 and Version 29 of DevNotes/DevGuide/CodingRules

Timestamp:

Jul 5, 2016 7:49:46 AM (8 years ago)

Author:

wojciech

Comment:

—

DevNotes/DevGuide/CodingRules

@@ -190 +190 @@
     * Remember to add files using git add before committing your changes.
     * Have a self-explanatory commit message. "Merged with master" is not sufficient. It is a good practice to do a git log before pushing to master and check for the top message. git commit --amend can be used to fix commit message if we are not satisfied with it.  
-    Using git branches is encouraged when developing new features or implementing significant changes. It is also a good habit to regularly merge you branch with master as well as push it Github (as a backup).
+    * Using git branches is encouraged when developing new features or implementing significant changes. It is also a good habit to regularly merge you branch with master as well as push it Github (as a backup).
     * When merging a branch with multiple commits use --squash or interactively rebase before pushing to master.