Verify and submit your contribution
Show the behavior your change enables or fixes, and give reviewers enough information to reproduce it.
Choose the relevant checks
| Change | Evidence to include |
|---|---|
| SDK behavior | Normal operation, completion results, failure handling, and shutdown with a real Runner |
| IPC | Shared vectors, native process tests, and interoperability between language implementations |
| Scaffold or bundler | A freshly generated project that builds, installs, and runs |
| Shared contracts | Agreement between definitions, examples, and every affected implementation |
Use the repository's pinned toolchains and verification commands. Start with focused checks while iterating, then run the applicable complete verification before proposing the change.
Prepare the pull request
- Explain the problem and the resulting behavior.
- List the checks run and the platforms tested; identify any untested platforms.
- Include reproducible evidence for runtime or interoperability changes.
- Update affected examples and documentation, and retain license and attribution notices.
Repository instructions
- Contributing — setup, coding conventions, and verification commands.
- SDK contract — SDK and generated-project acceptance requirements.
- IPC contract — protocol and cross-process checks.
- CI configuration — the project's automated platform checks.
Submit the change to apache/bifromq-tenon.