Contributing to HamavaELV Projects

Thank you for helping improve HamavaELV software and documentation.

Before you start

• Search existing issues and pull requests before opening a new one.
• Use an issue or internal work item for changes that affect architecture, security, data, or public behavior.
• Never include credentials, personal data, customer information, production logs, or internal network details.

Development workflow

1. Create a focused branch such as feat/..., fix/..., docs/..., or chore/....
2. Keep commits small, descriptive, and reviewable.
3. Add or update tests for behavior changes.
4. Update documentation and configuration examples when needed.
5. Open a pull request using the organization template.
6. Address review feedback and ensure required checks pass.

Pull request expectations

A pull request should explain the problem, the chosen solution, testing performed, operational risk, rollout needs, and any follow-up work.

Security-sensitive changes must follow least-privilege principles and must not weaken authentication, authorization, validation, secret handling, logging, or auditability.

By contributing, you agree that your work may be used under the license and terms of the target repository.