Branching Conventions

Flxbl follows the below branching conventions when they are creating branches.

Commit Message

We typically prefer (feature/bugfix/chore) branches be merged to the main/master or release branches using squash as the option. When it is being merged, most git repository systems allow to combine and edit the commit messages. The commit messages from multiple commits in feature branch should be cleaned up and should follow the similar format

[XYZ] Short Commit Message
- Commit Details
- Commit Details

In the above example [XYZ] denotes the work item number in the issue registry and is utilized by Flxbl tools to generate meaningful change logs.

Last updated