Tomas DvorakandDevin
420502eec1
- primora CLI + @primora/mcp server over generated client - auth users admin panel, mobile bottom nav - release workflow: GHCR images, compiled binaries, npm tarballs - fix gzip Content-Length truncation, nginx upstream re-resolution Authored By: TDvorak <[email protected]> Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
1.6 KiB
Contributing
Setup
See QUICK_START.md. The short version:
cp .env.example .env
docker compose up -d --build
For native development run only the infrastructure in Docker
(docker compose up -d postgres dragonfly mailpit) and start the three
services yourself.
Workflow
-
Fork, branch from
main, keep changes scoped. -
Run the quality gate before opening a PR:
npm run checkThis runs backend tests, the frontend typecheck, all workspace builds, and verifies generated code has not drifted.
-
If you changed database queries or migrations, run
npm run generate:sqlc. If you changedapps/backend/openapi/openapi.yaml, runnpm run generate:client. Commit the regenerated output with your change.
Conventions
- Generated code is never hand-edited —
packages/api-client/src/generatedandapps/backend/internal/database/dbare outputs, not sources. - Go —
gofmt,go vetclean; table-driven tests where they fit. - SolidJS — Composition via signals,
<Show>/<For>control flow, no manual DOM manipulation. Styles come from the design tokens inapps/frontend/src/index.css— new colors/surfaces belong there, not in ad-hoc hex values. - API changes — update
openapi.yamlfirst, then implement. The spec is the contract. - Keep commits focused; describe why, not what.
Reporting bugs
Open an issue with the failing endpoint or view, what you expected, what you
got, and docker compose logs output for the relevant service.
Security
Do not open public issues for vulnerabilities — see SECURITY.md.