Skip to main content

Contributing

Guidelines​

Contributing to this project should be as easy and transparent as possible, whether it's:

  • Reporting a bug
  • Discussing the current state of the code
  • Submitting a fix
  • Proposing new features

Getting started​

Set up the project with ./scripts/setup.sh.

GitHub is used for everything​

GitHub is used to host code, to track issues and feature requests, as well as accept pull requests.

Pull requests are the best way to propose changes to the codebase.

  1. Fork the repo and create your branch from develop
  2. If you've changed something, update the documentation and add an entry under [Unreleased] in the CHANGELOG.md.
  3. Make sure your code lints with ./scripts/lint.sh.
  4. Test your contribution.
  5. Issue that pull request!

Report bugs using Github's issues​

GitHub issues are used to track public bugs. Report a bug by opening a new issue; it's that easy!

Write bug reports with detail, background, and sample code​

Great Bug Reports tend to have:

  • A quick summary and/or background
  • Steps to reproduce
    • Be specific!
    • Give sample code if you can
  • What you expected would happen
  • What actually happens
  • Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports. I'm not even kidding.

Use a Consistent Coding Style​

Use ruff for formatting and linting and ty for type checking. Run all linters at once with:

./scripts/lint.sh

See CLAUDE.md for the project rules.

AI assistant​

The project only uses Claude Code as AI assistant. Its rules are in CLAUDE.md, tests/CLAUDE.md, website/CLAUDE.md and the skills in .claude/skills/.

Test your code modification​

To test the code we use pytest:

uv run pytest

The test coverage must stay at 100%, so every new code path needs a test.

Large expected values are stored as syrupy snapshots in __snapshots__ folders. After an intended change, update them and review the diff:

uv run pytest -n0 --snapshot-update

License​

By contributing, you agree that your contributions will be licensed under its Apache License.

KEBAKEBALatest version on PyPI

An asynchronous Python client for the KEBA KeEnergy Web HMI, used by the Home Assistant integration.

A community project, not affiliated with or endorsed by KEBA. KEBA is a registered trademark of its owner.

Requires Python 3.11 or newer.

View source on GitHub
View known issues
Request a feature
View on PyPI
Changelog

Maintainer

@mh-superbox

On this page