---
title: MGI - AppDev Git Standard
tags: Git Standard
description: MGI AppDev Git Standard.
---

<div style="text-align: center">
MGI - AppDev Git Standard
</div>

---

---

## Git Standard
---
### Standard branch name

- f_purpse/version/description = new feature for existing project, sprint for development
- b_purpose/issue id/description = bugs (any issue under development server)
- h_purpose/issue id/description = hotfix (any issue production server)

---
### Standard commit message

commit message should consist of 3 parts

- <type> - the ype of the made changes. Should be one of:
- feat - some feature development
- fix - bug fix
- docs - change in documentation
- style - formating changes
- refactor - changes those do not fix a bug or implement a feature. Simple refactoring
- test - changes to tests or addition of new ones
- chore - any other changes, not affecting code
- <scope> - here you define scope you can think of.
- <subject> - there are different methodologies to write the subject, but the main rules are as follows
- use imperative, present tense. "fix " not "fixed", "add" not "added". By the way, git also uses this convention for its own pre-formateed message ("Merge pull request...")
- dont's capitalize first letter
- do not dot(.) at the end of subject