Skip to content

📝 Branch naming conventions #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 20, 2024
Merged

📝 Branch naming conventions #23

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ded692c
📝 Created branch naming conventions
BestUsernamEver Feb 17, 2024
5a80cc6
📝 Updated branch documentation
BestUsernamEver Feb 17, 2024
ea3f28a
:memo: Fixed indentation in contributing TOC
BattleCh1cken Feb 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,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)!