dbt - Documentation

Contributing to dbt

How to contribute


We welcome PRs! We recommend that you log any feature requests as issues and discuss implementation approach with the team prior to getting to work.

To get started with a code contribution to dbt, clone the dbt GitHub repository and be sure to check out the technical contributing guide.


Documentation for dbt is written using readme.io: you can use the Suggest Edits tool to suggest edits, and someone from the dbt maintainers will review your suggestions.


If you have a suggestion or a bug to report, we'd love to hear it on. Please feel free to create an issue documenting your feature request or bug report. Please check for existing issues before creating a new one!


Looking for a way to contribute without writing code? Hang out with us in the dbt Slack and jump into a discussion! We always love hearing from dbt users.


Did you do something cool with dbt? Share that knowledge with the community! All posts, big and small, are welcome in the dbt Discourse.

Updated about a month ago

Contributing to dbt

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.