Thanks for helping make Frame better. We welcome contributions of all sizes: docs, examples, tests, new integrations, and core features.
High-impact contributions that improve usability and adoption:
- Clear onboarding docs, tutorials, and recipes
- Example services that demonstrate real patterns
- New Go Cloud drivers (queue, cache, datastore)
- Middleware, interceptors, or plugins
- Testing utilities and benchmarks
- Performance or reliability improvements
AI-assisted contributions are welcome. If you use AI tools, please:
- Verify behavior locally and include test coverage when relevant
- Avoid copy-pasting unverified output into production code
- Clearly describe what the change does and why
- Include any prompts or tool notes if they help reviewers understand the change
- Fork the repo and create a branch.
- Make changes with tests when possible.
- Run:
go test -json -cover ./...- Open a pull request with a clear description, screenshots/logs if helpful.
- Keep APIs simple and composable
- Prefer explicit configuration via interfaces
- Avoid breaking changes unless clearly justified
- Keep docs up to date with code changes
When filing issues, include:
- Frame version or commit hash
- Reproduction steps
- Logs or stack traces
- Environment details (Go version, OS)
By contributing, you agree that your contributions will be licensed under the repository’s license.