# Contributing to bdk_turso
Contributions are welcome. Please follow the BDK [Code of Conduct](https://github.com/bitcoindevkit/bdk/blob/master/CODE_OF_CONDUCT.md).
## Start with an issue
Open an issue before starting work, and wait for the project owner's feedback on the proposed change. Pull requests should address an existing issue and include a `Closes #<issue-number>` reference. This helps agree on scope before implementation and keeps changes coordinated.
Use the bug report or feature request issue form when opening an issue. For security-sensitive reports, do not post secrets, wallet data, or vulnerability details publicly.
## Tests
Tests are expected when a change alters runtime behavior, persistence semantics, or error handling. Documentation, formatting, and copy-only changes (including changing displayed text without changing program logic) do not need tests. Don't add tests solely to assert wording.
## Local checks
For code changes, run the checks relevant to your change. The CI workflow runs:
```sh
cargo fmt --all -- --check
cargo test --all-targets --locked
cargo check --no-default-features --locked
```
Please include the checks you ran in your pull request description, and note any that were not applicable or could not be run.