This document defines our standards for naming code branches, commits, and tickets. Following these conventions helps keep our workflow clean, organized, and easily traceable across tools like GitHub, Jira, and Slack.

Table of contents

🧠 GitHub – Branch Naming

All branches must follow this format:

feat/yourname/feature-name
fix/yourname/bug-description
chore/yourname/task-name

Examples:

🔹 Use lowercase and hyphens (-) to separate words. 🔹 Replace yourname with your actual GitHub or team-recognized name.

✅ Git Commit Messages

Start each commit with a keyword + Jira ticket ID (if applicable):

feat: implement login modal [CC-12]
fix: correct typo in user schema [CS-4]
chore: cleanup unused styles

🔸 Use present tense (add, fix, not added, fixed) 🔸 Include the ticket reference when relevant

📌 Jira Tickets

We use Jira ticket codes to organize tasks by scope:

Prefix Meaning
CC- Candido Client (frontend/UI work)
CS- Candido Server (backend/API work)
CD- Candido DevOps (infra, CI/CD, cloud)

🧩 When unsure of the ticket type, ask in #develop