Skip to main content

Git Workflow & Pull Request Guidelines

We follow a GitFlow-inspired branching strategy designed for continuous integration.

1. Branch Naming Conventions​

  • Features: eature/UC-ticket-id-brief-description (e.g. eature/UC-1204-agent-leaderboard)
  • Bugfixes: ix/UC-ticket-id-brief-description (e.g. ix/UC-1250-call-duration-sync)
  • Hotfixes: hotfix/v1.0.1-patch-name
  • Releases: elease/v1.1.0

2. Commit Message Standards​

We adopt the Conventional Commits specification:

  • eat: add dynamic dropdown cascade support in CRM
  • ix: prevent race condition in agent status heartbeat

efactor: optimize call segment join query

  • docs: update 3CX socket reconnection guide

3. Pull Request Requirements​

Before requesting a review:

  1. Ensure all linter checks and unit tests pass ( pm test, pm run lint).
  2. Provide a clear PR description explaining What changed and How to test.
  3. Include screenshots or loom video for UI updates in uc-enterprise-web.
  4. At least 1 Senior Engineer approval is required before merging to develop or main.