Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

You can contribute in many ways:

Types of Contributions

Report Bugs

Report bugs at https://github.com/ragnarok22/cryptobot_python/issues.

If you are reporting a bug, please include:

Your operating system name and version.
Any details about your local setup that might be helpful in troubleshooting.
Detailed steps to reproduce the bug.

Fix Bugs

Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.

Implement Features

Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.

Write Documentation

CryptoBot Python could always use more documentation, whether as part of the official CryptoBot Python docs, in docstrings, or even on the web in blog posts, articles, and such.

Translate Documentation

Help make CryptoBot Python accessible to non-English speakers by contributing translations! See the Translation Guide in the documentation for a complete guide on translating the documentation into other languages.

Submit Feedback

The best way to send feedback is to file an issue at https://github.com/ragnarok22/cryptobot_python/issues.

If you are proposing a feature:

Explain in detail how it would work.
Keep the scope as narrow as possible, to make it easier to implement.
Remember that this is a volunteer-driven project, and that contributions are welcome :)

Get Started!

Ready to contribute? Here’s how to set up cryptobot_python for local development.

Fork the cryptobot_python repo on GitHub.

Clone your fork locally:

$ git clone git@github.com:your_name_here/cryptobot_python.git

Install your local copy with uv. This is how you set up your fork for local development:
```
$ cd cryptobot_python/
$ uv sync
```
Create a branch for local development:
```
$ git checkout -b name-of-your-bugfix-or-feature
```
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests:
```
$ make lint
$ make test
```
To run integration tests (network + API token required):
```
$ pytest --run-integration tests/test_sync_client.py
```

Commit your changes and push your branch to GitHub:

$ git add .
$ git commit -m "Your detailed description of your changes."
$ git push origin name-of-your-bugfix-or-feature

Submit a pull request through the GitHub website.

Pull Request Guidelines

Before you submit a pull request, check that it meets these guidelines:

The pull request should include tests.
If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.md.
The pull request should work for Python 3.10, 3.11, 3.12, 3.13, and 3.14. Check the GitHub Actions workflow and make sure that the tests pass for all supported Python versions.

Tips

To run a subset of tests:

$ pytest tests/test_specific.py

Deploying

A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.md). Then run:

$ # Update version in pyproject.toml manually
$ git add pyproject.toml
$ git commit -m "Bump version to <new-version>"
$ git tag "v<new-version>"
$ git push
$ git push --tags

GitHub Actions will then deploy to PyPI if tests pass.