The project can be divided into PC end, IOS end, Android end and Java back end

Which is divided into development version, test version, online version, stable version (0)

By function: primary site, sub-site, and private cloud mode

Therefore, a reasonable layout can make team collaboration more efficient and development experience better.

Android Version Management

  1. Original Android Repository: Front-end – Android Side code (V1.0)[pause]
  2. New Android repository address: Front-end -Android side code (V2.0 version)
  3. Provision: a publish branch (read only)
  4. App store releases must have a relase version printed as a distribution
  5. The daily tag tag is convenient for quick rollback versions
Git add. Git commit -m "commit" -b "git chekout" -b "yspdev" git tag v5.8.0-snap Git tag v5.8.0-snap git tag v5.8.0-snap git tag v5.8.0-snap git tag v5.8.0-snap git tag v5.8.0-snapCopy the code

At this point, you can be sure that the version in APPstroe has a corresponding relase version in the Git repository

At this time, if the online product V5.8.0 found a BUG, need to be fixed immediately, and our local development branch has developed to 5.8.0.899

Git add. Git commit -m Git fetch origin tag v5.8.0-realse "git push origin yspdev yspdev git fetch origin tag v5.8.0-realse Git checkout -b v5.8.0_bug_branch_temp1 v5.8.0-realse[version snapshot] Git checkout master git checkout master git checkout master Git merge v5.8.0_bug_branch_temp1 # Git merge v5.8.0_bug_branch_temp1 # Git merge Request, merge master branch to publish Realse branch # and relase branch, Git checkout yspdev # Merge master branch into current branch git merge master #Copy the code