Why is this a good commit message?
- add runtest.bat- short and precise
- tells what is added in committed
Branching
- Push branch to fork
- We can make pull request from the fork
- Branching allow us to try new stuff without working on master
- Developers can look at the branch after pulling and give feedback
- Can reply the comments of that pull request
- Pull request auto update, there is no need to repull
- Pull request gets updated when my branch is updated (commited to remote repo)
Team work
- It is very hard to syncronise on project repo
- Everytime when do code, first thing is to fetch changes from upstream
- Change code
- Never leave unsync change, always commit it
- Merge if need, ensure that your changes is uploaded to repo
- this avoid potential merge commits
Static analysis
- IDE highlights and marks errors or points to take notes
- This can happen even without running
- e.g:
- Problems
- Uncaught error
- Checkstyle
- Unused variables
Control code
Regression is the unintended and undesirable side effect of fixing bugs
- Proper testing
- Auto testing
- Regression testing
Submitting patches
- Ensure no regression
- Automatic test
UML Modelling
- Not many company in lower end use it
- Model structure
- Model behavior
No comments:
Post a Comment