You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: A user makes changes to their models and they see how code changed, models impacted, and unit tests run. However, it's still opaque as to how exactly data has changed. It's hard to review the PR with confidence without running ad hoc queries to know the differences between dev and prod.
Solution: Add a config option in addition to a tabbed output in the GitHub Action formatted output that shows the data diff stats automatically and have it automatically diff by picking up the grain to run the data diff.
Example config:
cicd_bot:
type: githubmerge_method: squashenable_deploy_command: trueenable_table_diff: true # this is the oneauto_categorize_changes:
external: fullpython: fullsql: fullseed: full
Note: probably want to prevent showing sample data and give a warning or error to the user that this is not allowed in the official ci/cd bot for security reasons.
The text was updated successfully, but these errors were encountered:
Problem: A user makes changes to their models and they see how code changed, models impacted, and unit tests run. However, it's still opaque as to how exactly data has changed. It's hard to review the PR with confidence without running ad hoc queries to know the differences between dev and prod.
Solution: Add a config option in addition to a tabbed output in the GitHub Action formatted output that shows the data diff stats automatically and have it automatically diff by picking up the
grain
to run the data diff.Example config:
Note: probably want to prevent showing sample data and give a warning or error to the user that this is not allowed in the official ci/cd bot for security reasons.
The text was updated successfully, but these errors were encountered: