Conversation
Tutorial for setting up Recce Cloud when dbt runs on dbt Cloud, covering artifact retrieval via dbt Cloud API and GitHub Actions workflow configuration. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Restructure setup guidance into nested decision tree - Question 1: Where dbt runs (self-hosted vs dbt Cloud) - If self-hosted: sub-options for GitHub Actions vs GitLab/CircleCI - Question 2: Environment complexity (simple vs advanced) - Link to dbt Cloud Setup for platform users - Link to Environment Setup for advanced configurations
- Add dbt Cloud Setup to mkdocs.yml navigation - Update setup-cd and setup-ci links to new location (2-getting-started/)
- Add problem statement to dbt-cloud-setup opening - Remove redundant content between intro and goal - Spell out PR and CI/CD acronyms on first use - Fix "bolded steps" references to explicit commands - Improve image alt text for accessibility - Rename "Related" to "Next steps" with descriptive links Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
even-wei
requested changes
Mar 3, 2026
Contributor
even-wei
left a comment
There was a problem hiding this comment.
- Warehouse connection is not required here because it runs in Recce Cloud now. The CI job only need to download artifacts from dbt Cloud and upload to Recce Cloud.
- We don't need "Run Recce validation", "Generate Recce summary", and "Comment on pull request" steps. Use
recce-cloud upload --type prodandrecce-cloud upload.
…load Based on review feedback: - Remove warehouse connection requirement (runs in Recce Cloud) - Remove "Run Recce validation", "Generate Recce summary", "Comment on PR" steps - Split into two workflows: base (CD) and PR (CI) - Use recce-cloud upload --type prod for base - Use recce-cloud upload for PR Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
ijac13
commented
Mar 3, 2026
Contributor
Author
There was a problem hiding this comment.
@even-wei Thanks for the feedback! Updated in 3afff2f:
- ✅ Removed warehouse connection requirement - CI job only downloads artifacts from dbt Cloud and uploads to Recce Cloud
- ✅ Removed "Run Recce validation", "Generate Recce summary", and "Comment on pull request" steps
- ✅ Split into two workflows:
- Base workflow (
recce-base.yml):recce-cloud upload --type prod - PR workflow (
recce-pr.yml):recce-cloud upload
- Base workflow (
even-wei
approved these changes
Mar 3, 2026
Contributor
even-wei
left a comment
There was a problem hiding this comment.
LGTM on technical parts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Create setup guide for using Recce Cloud with dbt Cloud CI/CD. Covers retrieving artifacts via dbt Cloud API instead of generating them locally.
Scope
2-getting-started/dbt-cloud-setup.mdQuality Checks
Content Changes
Before → After
dbt-cloud-setup.mdReview status:
Change Review
I reviewed all changes and confirm:
Review notes: QA and AISEO checks passed with minor issues. Line 7 uses "pull request" instead of "PR" (should fix). Missing recency signal is non-blocking.
Test plan
🤖 Generated with Claude Code