Pull requests are welcome! We appreciate your contributions to making luaz better.
- Description:
- Add a brief description that articulates the motivation and explains what the change does and why it is needed
- Code Quality:
- Make sure the change is cleanly written and follows existing code patterns
- Always run
zig fmt .before committing to ensure consistent formatting - Follow the idiomatic Zig patterns established in the codebase
- Testing: All changes must be covered by unit tests
- Run tests with
zig build test - Ensure your code is actually executed in tests (Zig skips unused code during compilation)
- Run tests with
- Documentation: Update relevant documentation using Zig's doc comment syntax (
///) if your change affects public APIs - Issue References: If your PR fixes an existing issue, mention it in the PR description (e.g., "Fixes #123")
- Fork the repository
- Create a feature branch for your changes
- Make your changes following the guidelines above
- Run
zig fmt .to format your code - Ensure all tests pass with
zig build test - Submit a pull request with a clear description
Thank you for contributing to luaz!