Skip to content

Dev Guidelines

Paul Cullen Rowe edited this page Jan 23, 2019 · 5 revisions

Tech Stack

  • Front-End
    • Vue.js
    • Typescript
    • CSS Preprocessor: SCSS
    • DECIDE: Testing Framework [Jest, Mocha]
  • Back-End
    • Golang
    • DECIDE: [GraphQL, GRPC, JSONApi]

Environments

  • Mobile First
  • DECIDE: Browsers [All, Chrome, Safari, Firefox]

Branching Strategy - Git Flow

Git Flow keeps branches organized with the following 5 branches/prefixes:

  • master <- (releases get pushed here)
  • develop <- (feature branches get pushed here)
  • release/*
  • feature/* <- (most work is here)
  • hotfix/* <- (production bugfixes)

In short, most work will be on a feature/ branch, which comes off of develop. For example, feature/11-custom-map-points, where 11 indicates the issue number, followed by a short description.

Clone this wiki locally