Thanks for contributing.
Please keep these checks green:
swift test
(cd Examples/SwiftUIExample && swift test)
(cd Examples/PreviewInjectionExample && swift test)
swift run InnoDI-DependencyGraph --root . --validate-dag
Benchmarks/run-validation-bench.sh --preset ciUpdate docs in the same change when behavior changes:
README.mdREADME.ko.mdSources/InnoDI/InnoDI.docc/Validation.mdSources/InnoDI/InnoDI.docc/PolicyBoundaries.mdSources/InnoDI/InnoDI.docc/ModuleWideInitDetection.md
- Keep changes scoped and explain user-facing behavior changes.
- Add or update tests for validation, diagnostics, graph output, or examples when behavior changes.
- If benchmark artifacts or schema expectations change, update
RELEASING.mdandMIGRATION.md. - If performance changes intentionally, refresh the relevant baseline and call it out in the PR description.
- Use issues for reproducible bugs, missing diagnostics, or feature requests.
- Include sample containers or CLI output when reporting graph or validation problems.