Thanks for helping improve Hyperstrate.
- Fork the repository.
- Create a feature branch:
git checkout -b feat/my-change. - Make focused changes with tests where behavior changes.
- Run the relevant checks:
go test ./...
go build ./cmd/api ./cmd/worker ./cmd/migrate- Open a pull request and describe the behavior change, tests, and any migration or security impact.
- Keep pull requests focused on one topic.
- Include tests for bug fixes and behavior changes.
- Regenerate Swagger docs with
make swaggerafter changing handlers or DTOs. - Do not commit
.env, local databases, build artifacts, API keys, or provider credentials. - Open an issue before large architectural changes so maintainers can discuss the direction.
Follow the existing module layout under internal/modules/<name>/: domain, application, infrastructure, interfaces, and module wiring.