Thanks for contributing.
Fusion values simple, maintainable changes over complex abstractions.
- Search existing issues/PRs first.
- For bugs, include reproducible steps, expected behavior, and actual behavior.
- For features, explain the concrete use case and user value.
Requirements:
- Go
1.25+ - Node.js
24+ - pnpm
Install dependencies:
# frontend
cd frontend && pnpm installBackend uses Go modules and installs dependencies automatically via go tooling.
cd backend
go test ./...
goimports -w .
go build -o /dev/null ./cmd/fusioncd frontend
npx tsc -b --noEmit
pnpm lint
pnpm buildIf your change is scoped, you can run a smaller test subset first, but run the relevant final checks before requesting review.
- Keep PRs focused. One PR should solve one clear problem.
- Explain why the change is needed, not only what changed.
- Include screenshots/GIFs for UI changes.
- Link related issue(s).
- Mark as Draft if not ready for review.
- If you use AI tools, review and validate outputs carefully before submission.
- Prefer readable, self-explanatory naming.
- Avoid over-engineering.
- Add comments only for non-obvious logic or decisions.
- Keep docs and API behavior aligned when changing contracts.