📝 Branch naming conventions (#23)

* 📝 Created branch naming conventions

* 📝 Updated branch documentation

* 📝 Fixed indentation in contributing TOC

---------

Co-authored-by: BattleCh1cken <[email protected]>

Author: BestUsernamEver

.github/CONTRIBUTING.md

@@ -17,14 +17,15 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 ## Table of Contents
 
 - [I Have a Question](#i-have-a-question)
-- [I Want To Contribute](#i-want-to-contribute)
-- [Reporting Bugs](#reporting-bugs)
-- [Suggesting Enhancements](#suggesting-enhancements)
-- [Your First Code Contribution](#your-first-code-contribution)
-- [Improving The Documentation](#improving-the-documentation)
+  - [I Want To Contribute](#i-want-to-contribute)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+  - [Your First Code Contribution](#your-first-code-contribution)
+  - [Improving The Documentation](#improving-the-documentation)
 - [Style Guides](#style-guides)
-- [Typst Code](#typst-code)
-- [Commit Messages](#commit-messages)
+  - [Typst Code](#typst-code)
+  - [Commit Messages](#commit-messages)
+  - [Branches](#branches)
 
 ## I Have a Question
 
@@ -176,6 +177,16 @@ Commit messages should be short and descriptive. This project follows the [Gitmo
 
 Use the unicode version of the emojis wherever possible. This means you should write 🔥 instead of :fire:.
 
+### Branches
+
+Branches must have labels depending on what the branch changes to the project.
+
+- Fix: improves a pre-existing feature
+- Feature: adds a new feature
+- Theme: adds a new theme
+
+A complete branch name would be **theme/your-theme-name** or **feature/theme-cover**.
+
 ## Attribution
 
 This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!