Mengjia( Miya) Chen

Working in a team, we don't want to get troubles for our teammates. As a developer, it is possible to break the whole environment for personal mistakes, which you don't want to see. Things before push your code. 1. Run it locally to make sure it can run successfully. 2. Format the code and optimize the package. 3. Check other dependent Projects

Some common usage of git with SourceTree -> pull to local pull to local  - if no conflict -> pull successfully  - if has conflict     option 1. commit to local repo -> stash changes  -> pull    option 2. prof read  -> push to remote If already commit, but don't want to push the code to the remote. :) Simple delete ur local repo, and clone again.

Created on 3rd Oct 2018 Some notes: JDK setting in IntelliJ  - menu project structure-> project -> modules Maven  setting.xml    profile    username & password -clean: clean all files generated by mvn -compile: compile -test: run test -package: compile and generate executed file (e.g.war/ .jar) -install: install to the local machine -deploy: deploy to remote server Sourcetree  checkout branch In sourcetree, we can see both local and remote repositories. After clone the repo to local, there is only one branch in local, that is master. If you want to checkout to another branch. Go to the remote and right click the branch you want to switch to.  Select Checkout new branch. Then the new branch will be created locally.  git stash Swagger in body? in path time stamp: number Springboot injection annotation @autowired --- 12th Oct Jenkins pipeline Sonar (code report) Jacoco plugin: code cov...