GIT Version Control

We track all the development process using a version control like GIT.

Git Workflow for Projects

• All projects need a repository for tracking the development changes.
• If the project is NEW we need to create a repo in the Minnek Github Organization.
• All projects must contain: develop and master branches.
• Master Branch - Must be a copy from the production site.
• Develop Branch - Must contain all the finishes features.
• Tests Branch - Must contain all the opened features to test before merging to develop or master branch.
• All issues created on JIRA need to follow the Git Flow methodology.

Illustration of the Git Workflow

Branch strategy

For every new task you need to create a feature banch ex: feature/PROJECT_CODE-{TASK-ID}. In a real world example for a current project called DENTAKIT, the code for the project is DEN and the task ID will be 100 so you will get something like feature/DEN-100.

Why this is important?

Because in that way we can track all the work that come from a repo in the same task in JIRA and we can understand on what's going on in the project.

Pull Request

After you finished a feature you need to create a PULL REQUEST and assign the code reviewer on your project.

• If the code reviewer approved the work, now you can merge the changes to the develop branch.

• NOTE: never merge changes from features to master branches and never make commits direct to these branches. See the git flow guide to know how to work with branches.

See the internal code review guidlines.