Contributing

Branch workflow

1. Create a feature branch from main.
2. Make focused changes with passing local checks.
3. Open a merge request on GitLab.
4. Ensure CI passes (lint, typecheck, test, build).
5. Squash or merge per team preference after review.

Conventional commits

Use Conventional Commits:

Type	When
chore	Tooling, workspace setup, DX
feat	New app or package
feat(scope)	Scoped feature (e.g. feat(api), feat(web))
docs	Documentation site or content
test	Test-only additions
ci	CI/CD pipeline changes

Examples:

feat(web): scaffold React frontend shell
ci: add GitLab typecheck jobs for api and web
docs: document deployment variables

Commits should be signed (SSH or GPG) per repository policy.

Git hooks (Lefthook)

pnpm install runs lefthook install via the root prepare script.

Hook	Behavior
pre-commit	oxfmt + oxlint on staged files; pnpm typecheck when .ts files change
pre-push	format:check, lint:check, typecheck

Run hooks manually:

pnpm exec lefthook run pre-commit
pnpm exec lefthook run pre-push

Code style

• Lint: oxlint (type-aware via oxlint-tsgolint)
• Format: oxfmt (Prettier-compatible)
• Types: tsgo (@typescript/native-preview) — astro check for docs

Match existing patterns in the package you are editing. Prefer extending shared packages over duplicating logic in apps.

Adding shadcn components

From the web app, install shared primitives into packages/ui:

pnpm --filter @quiz-builder/web exec shadcn add card

App-local components stay in apps/web/src/components/.