---
title: Developer Guides
slug: dev.docs.oelite.com
createdAt: 2022-05-08T19:14:44.000Z
---

This is a general guide on how we code in the team so everyone can follow the same standard and coding pattern & structure.

# Git Repository & Branches

We use GitLab for storing our code (Code Base [https://code.webcider.com ](#)).&#x20;

## Branches:

- **branches for tasks:&#x20;**&#x66;or each task you work (including tasks from https\://projects.webcider.com), please always create a new issue in GitLab and then let GitLab to generate a new branch for the specific task. By doing such, you'll be working under the newly created branch and submit a merge request to **develop** branch when you complete the task.
- **master** branch: we only merge production ready code to master branch. In general, master branch is supposed to be production only code base, and some of the projects has automated build & deployment scripts for continous integration & deployment. This is normally handled by our developer lead manually, so please make sure <u>never merge request to master branch</u>.
- **develop** branch: this is the branch where we hold the latest approved code.&#x20;

## Merge Requests:

As mentioend above, always create new issue in GitLab to work on a branch that's created specifically for the issue.



# Coding Standards & Naming Conventions

