This page describes how to name branches and write commit messages to keep our Git history clean, structured, and collaborative.

🔤 Branch Naming Convention

Always name your branch using the following format:

feature/CND-123-short-description
bugfix/CND-123-short-description
refactor/CND-123-short-description

✅ Examples:

• feature/CND-105-user-registration-form
• fix/CND-202-email-validation
• refactor/CND-140-registry-refactor

Branches must be linked to the Jira ticket inside the task panel.

📘 Commit Message Guidelines

We follow structured guidelines to make our Git history clean and searchable. Below are the recommended resources for writing good commit messages.

1. European Commission – Git Commit Conventions: Official EU guide on writing commit messages and managing Git workflows in a public, reusable way.
2. Conventional Commits Specification: A standardized format for commit messages ideal for semantic versioning and changelog automation.
3. [FreeCodeCamp – How to Write Better Git Commit Messages](https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/**](https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/)): A practical guide with tips for writing clear, consistent Git commits.