Skip to main content

NCV GitLab Naming & Branching Convention

Status: ACCEPTED · Version 1.0 (2026-09-16) · Owner: EM (governance), enforced in review Applies to: all groups and repos on code.naudecoreventures.com

Groups

  • Top-level group = product/business name, lowercase, hyphen-separated: lyt-ning, synergy, kazang, gitlab-platform, leancore.
  • One top-level group per product; subgroups only for real sub-products, max 1 level deep.
  • No personal groups for product work; no empty placeholder groups older than 30 days (pre-staged shells must record their intended ADO mapping on the project board).

Repositories

  • Pattern: <product>-<component>-<type> — e.g. kazang-payment-gateway-api, synergy-core-api-v2, lytning-pos-flutter.
  • Types: api, web, flutter, lib, infra, docs.
  • Platform repos live under gitlab-platform: ci-templates, handbook, pilots suffixed -pilot.

Branches

  • Default branch: main, protected on every repo (Maintainer push/merge, no force-push). Legacy master is migrated to main during each repo’s next deliberate change; new repos are born on main.
  • feature/<ticket>-<slug> · fix/<ticket>-<slug> · release/x.y · hotfix/<slug>
  • Ticket references (DEV-/project key) are mandatory in branch names and MR titles.

Tags & versions

  • Semver vX.Y.Z. CI templates, handbooks, and release artifacts pin tagged versions — floating main includes are forbidden in pipeline includes.

Runners & CI

  • Runner naming: <group>-<purpose>-<nn> (e.g. kazang-build-01), group-scoped, tags per DEV-45 spec. Instance-scoped runners require written justification.
  • Pipelines include gitlab-platform/ci-templates@vX.Y.Z (pinned tag).
  • CI ends at build + push to the GitLab Container Registry / package feeds; deployment is GitOps/Flux; zero Kubernetes credentials in CI (posture rule, DEV-45 decision).

Access

  • Humans: least privilege; Developer cannot push main. Admin accounts do not do product work. 2FA enforced per instance policy once approved (WS7).