Update 'Contributing to Project: Serenity'

master
MathDev 1 week ago
parent e121ec5242
commit 2c07d58dfc

@ -22,22 +22,20 @@ Always create a new branch for your task or feature. **Never commit directly to
**Branch Naming Convention:** **Branch Naming Convention:**
The Types of Branches we use are as follows: * Feature
Format: feature/<name>
#### Feature
Format: feature/name
*Features will be used for adding new gameplay mechanics, UI updates, major changes.* *Features will be used for adding new gameplay mechanics, UI updates, major changes.*
#### Bugfix * Bugfix
Format: bugfix/name Format: bugfix/<name>
*Bugfixes will be used for fixing bugs that don't appear to be game/project breaking, and may not have been noticed early.* *Bugfixes will be used for fixing bugs that don't appear to be game/project breaking, and may not have been noticed early.*
#### Hotfix * Hotfix
Format: hotfix/name Format: hotfix/<name>
*Hotfixes are for fixing issues that prevent features from functioning. For example, missing dependencies etc.* *Hotfixes are for fixing issues that prevent features from functioning. For example, missing dependencies etc.*
#### Task * Task
Format: task/name Format: task/<name>
*Tasks are smaller updates. For example, adding a new static mesh, implementing an animation etc.* *Tasks are smaller updates. For example, adding a new static mesh, implementing an animation etc.*
When you're sure about the branch type, checkout the branch. As an example: When you're sure about the branch type, checkout the branch. As an example:
@ -95,8 +93,6 @@ We review all changes before they're merged into the main branch. This is to ens
**Branch Naming Convention:** **Branch Naming Convention:**
The Types of Branches we use are as follows:
* Feature * Feature
Format: feature/<name> Format: feature/<name>
*Features will be used for adding new gameplay mechanics, UI updates, major changes.* *Features will be used for adding new gameplay mechanics, UI updates, major changes.*

Loading…
Cancel
Save