Skip to main content

5. CI quality gates and conventional commits

Date: 2026-05-03

Status​

Accepted

Context​

We want fast feedback on every change and a readable history for humans and automation. Untyped or untested merges increase rework and risk—particularly when AI-generated patches land frequently.

Decision​

  • CI must run automated checks on pull requests and protected branches. At minimum for this repository: install with a frozen lockfile, TypeScript check where applicable, and a successful docs build for apps/docs. Expand gates (lint, tests, SAST) as applications add them.
  • Prefer Conventional Commits for commit messages and semantic versioning for published packages when we release libraries or apps with versioned APIs.

Consequences​

  • Positive: Broken TypeScript or broken docs builds cannot merge silently.
  • Positive: Commit and release history stays machine-parseable for changelogs and tooling.
  • Tradeoff: Contributors learn commit conventions; we document examples in AGENTS.md and team norms.