Skip to content


Here's how you can contribute your Spell on GitHub.

Fork the Spellbook GitHub Repo and open a Pull Request.

When you’re happy with your Spell, from a fork of the Spellbook GitHub Repo, open a Pull Request.

This step is non-specific to Spellbook. So I will farm out the explanation to Jake Jarvis who has an excellent step by step guide to forking and committing a Pull Request to a public GitHub repository.

Once you’ve opened your pull request, fill out the pull request template and tag the duneanalytics/team-data-experience team-data-experience.

We will review your code and run your tests. Our goal is to eliminate this step and provide a sandbox where you can run your Spells and tests directly. Unfortunately (fortunately?) GitHub rightfully blocks secrets from pull requests from forks which is why we can’t run DBT from your original pull requests.

Dune will merge and deploy

If everything looks good, Dune will merge your changes and deploy them to production. Your Spells will be visible on Dune V2 Data Explorer under Spells.

And ta-da! You are a Spell casting wizard.