CDNManager/CONTRIBUTING.md

Contributing

Gitflow

• main — production; merges only from release/* and hotfix/*
• develop — integration branch (default for development)
• feature/* — feature/[issue-id]-description from develop
• release/vX.Y.Z — stabilization from develop
• hotfix/vX.Y.Z — urgent fixes from main

Commits

Обязательно Conventional Commits — иначе semantic-release на main не создаст тег и не опубликует Docker-образ.

Формат: type(scope): описание на русском

Type	Релиз
feat	minor
fix, perf, ci, refactor	patch
docs, chore, test, style, build	нет

Scope — один идентификатор без запятых (web, api, ci, docker, fleet).
Локально: husky .husky/commit-msg → commitlint. Шаблон: .gitmessage (git config commit.template .gitmessage).
Правила Cursor: .cursor/rules/commit-messages-ru.mdc.

Плохо: Init Commit, Update CDN Manager: Add….
Хорошо: feat(fleet): добавить CRUD нод и алиасов.

Pull requests

• Target develop for features; main for release/hotfix
• CI quality jobs (web, api) must pass
• At least one approval
• Rebase/merge when up to date with target branch
• Delete branch after merge

Versioning

• SemVer через semantic-release на push в main
• Не править версию вручную; тег vX.Y.Z ставит CI
• Подробнее: docs/releasing.md

Branch protection (Gitea)

Configure for main and develop:

• Require pull request reviews
• Require status checks (CI / quality jobs web, api)
• Require branches to be up to date
• No force push, no deletion

Local development

cp .env.example .env
pnpm install
pnpm --filter @cdnmanager/shared build
pnpm --filter @cdnmanager/db build

# API (:8080)
pnpm --filter @cdnmanager/api dev

# Frontend (:5173, proxies /api → :8080)
pnpm --filter web dev

Release process

Релизы делает workflow CD на push в main (semantic-release + bake). Не создавать ветки release/* и не bump'ать файлы версии вручную. См. docs/releasing.md.