Skip to content

Contributing

Thank you for your interest in contributing to heliaRT. This section covers the project's design, workflows, and processes.

  • Architecture

    Source layout, kernel wiring, and design principles.

    Architecture

  • Upstream Sync

    How the LiteRT for Micro replant works and blast-radius philosophy.

    Upstream Sync

  • Release Process

    release-please, version bumps, and artifact bundling.

    Release Process

Getting Started

  1. Open an issue describing what you want to contribute and why.
  2. Fork the repository and create a feature branch from main.
  3. Read the Architecture page to understand the source layout.
  4. Make changes following the guidelines below.
  5. Open a pull request against main, linking the issue with BUG=#nn.

PR Guidelines

  • One PR per concern — keep PRs small and focused.
  • Conventional commits — use feat:, fix:, chore:, docs: prefixes.
  • Pre-submit checks before submitting:
    • clang-format for C/C++ style
    • cpplint for lint issues
    • Run tensorflow/lite/micro/tools/ci_build/test_x86_default.sh for basic tests
  • Merge, don't rebase — do not force-push after review has started.

License & CLA

heliaRT is released under the Ambiq Apollo SDK License. By contributing, you agree your changes are licensed under the same terms.

A Google CLA is required for all contributions (inherited from upstream LiteRT for Micro).

Code of Conduct

We follow Google's Open Source Community Guidelines. Be respectful and constructive.