Thank you for your interest in contributing! These guidelines apply to all repositories under this account to ensure a consistent and secure contribution process.
- Contributions are welcome from everyone
- Keep discussions respectful and constructive
- Follow the repository's existing structure, style, and conventions
- Be concise in commits, pull requests, and comments - clarity over cleverness
- Create a branch for each feature or fix. Branches should be based on
masterand named descriptively (e.g.,feature/add-logging,fix/typo-readme) - Make atomic commits. Each commit should represent a single logical change with a clear message
- Open a Pull Request (PR). PRs should:
- Describe why the change is needed
- Reference related issues (if applicable)
- Pass all tests and checks before review
- Request a review if applicable, and respond politely to feedback. Maintainers may ask for adjustments before merging
All code should conform to the language's standard formatter and linting tools:
- Go:
go fmt,go vet, and the project's configured linters - JavaScript / TypeScript:
prettierandeslint - C / C++:
clang-format - Other languages: follow community-accepted style guides
Ensure that:
- Code builds successfully without warnings
- No trailing whitespace or unused imports remain
- Tests (if present) pass locally before submitting a PR
If the project includes tests:
- Add or update tests relevant to your changes
- Ensure tests run cleanly on all supported platforms
- Avoid introducing flaky or environment-dependent tests
- Update documentation, examples, or comments if your change affects usage or behavior
- Keep README or code comments accurate and minimal - avoid duplication across files
Contributions of any size - from typo fixes to new features - are appreciated. Be kind, stay curious, and help keep the ecosystem healthy and consistent.