Contributing

Branching Model

Naming Guidelines

We use a prefix-based branching model. Please name your branches as follows:

• feat/ for new features
• fix/ for bug fixes
• docs/ for documentation changes
• refactor/ for code refactoring
• chore/ for routine tasks

Example: feat/add-search-bar

Workflow

• Pull requests must be peer reviewed by one other contributor.
• Mention the issue / ticket number in the pull request description.
  • Example: Closes #123

Commit Message Guidelines

We follow the Conventional Commits specification:

• Type: feat, fix, docs, style, refactor, perf, test, chore.
• Subject: Use the imperative mood ("add" not "added"). Max 50 characters.
• Body: (Optional) Use it to explain the why and how, not the what.

Example: feat(locks): add ISEO sync endpoint