Git Workflow

Currently, our workflow is based on this model. To help follow that idea, we're using the gitflow tool.

After downloading the project, you should run:

$ git flow init

Which branch should be used for bringing forth production releases?
Branch name for production releases: [] master
Which branch should be used for integration of the "next release"?
Branch name for "next release" development: [master] dev
How to name your supporting branch prefixes?
Feature branches? [feature/]
Release branches? [release/]
Hotfix branches? [hotfix/]
Support branches? [support/]
Version tag prefix? []

The git-flow configurations will be saved on the .git/config file.

In case of make a mistake, you can run git flow init -f, which will force the reconfiguration.

You can start a new feature by using git flow feature start <feature_name>. Create a Pull Request for you new branch, and set the label as in progress.