# install dependencies
yarn
# start development server
yarn dev
We use the gitflow workflow this is also helpful.
- Development of features happens in branches made from develop called feature/ like feature/update-profile.
- When development is finished a pull request to develop is created. At least one person has to review the PR and when everything is fine the PR gets merged.
- The develop branch gets deployed to the stage environment by travis.
- To make a new release create a release branch called release/vX.X.X, also bump the version number in package.json in this branch.
- Create a PR to master which then also has to be accepted.
- Create a tag for this version and push the tag.
- Also merge back the changes (like the version bump) into develop.
- The master branch has to be deployed to the production environment manually.
We have a stage (develop) and a production (master) branch and environments where these branches will be deployed to.
- Is used to see changes to the code in effect in a "real" environment without the fear of breaking the production environment.
- Is the production environment, code lives in the "master" branch.