- Pull repo.
git clone [email protected]:kdlcruz/kdlcruz.git - Go to project.
cd kdlcruz - Install modules.
npm install - Start project.
npm start
We follow a very specific branching workflow. All new work is started br branching from staging into a branch that is either prefixed with feature/ or hotfix/ depending on whether it is feature/change that adds new functionality, or a bug fix to existing functionality.
A PR back to staging should be created right away and prefixed with [WIP] so other team members may track progress of your work. When the branch has passed your own QA, remove the [WIP] and request a review from a team member. Once the branch has been reviewed it can be merged by an approved admin.
These features and hotfix branches will be automatically deployed to their own isolated QA environment when push into GitHub. For example:
All merges into staging will be automatically deployed to our staging environment at https://staging-dot-kdlcruz-183808.appspot.com/
All branch name should be stricted to Alphabet, number and hyphen.
This project is heavily integrated with a CI/CD pipeline currently running on CircleCI. The app is deployed in Google App Engine.
master branch will only be used if the new features/hotfixes from staging passes from manual QA.
npm run test / npm run lint
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent