update full refresh #6817
Merged
update full refresh #6817
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
nataliefiann
approved these changes
Jan 24, 2025
There was a problem hiding this comment.
Hiya @mirnawong1
Thanks for this. I've approved this for you. I've left one suggestion
Kind Regards
Natalie
Co-authored-by: nataliefiann <[email protected]>
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.
this pr updates the full_refresh config doc by removing contradictory information.
it clarifies that if the config is set to
true, then dbt performs a full refresh, regardless if you pass the --full-refresh flag or not.confirmed with the dbt core team and tested
🚀 Deployment available! Here are the direct links to the updated files: