Skip to main content

🏷️ Naming Conventions

Consistent names improve searchability, automation, and reviews.

Branches​

Format: type/<short-topic>_YYYY-MM-DD Examples:

  • ✅ feat/button-focus_2025-08-20
  • ✅ fix/pp-dark-contrast_2025-08-21
  • ❌ mybranch / update

PR Titles​

  • feat: Improve button focus ring
  • fix: Correct PP Dark text contrast
  • docs: Update theming guidance

(Optional) Token names​

Prefer semantic tokens for UI usage:

  • color.text.primary, color.bg.brand, color.border.focus Avoid raw brand tokens in UI layers.

Commit messages​

  • Use imperative mood: add, fix, update.
  • Reference ticket IDs when relevant.

Name Conventions Guidelines

How to create names for Branchs? Depending on the Design System (The Wall or Abacus) you're working for, there are a number of rules you should always take into account when creating a name for a new branch.

The Wall

For The Wall, the composition of the branch name always is displayed with:

Pull Type

Designer name

Component name

Composition of the branch name

(signpost type) / designer-name _ Component name

Example of a branch name: feat/andreia_BubbleItem

Abacus

For Abacus, the composition of the branch name always is displayed with:

Pull Type

Designer name

Day+Month

Composition of the branch name

(signpost type) / designer-name _ Day+Month

Example of a branch name: feat/marta_26Jun