feature/update-definitions-feb-2025 #147
Merged
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
| @@ -14,6 +14,7 @@ | |||
| - Added information about manually configuring the `fivetran_platform_using_transformations` variable in the [DECISION LOG.](https://github.com/fivetran/dbt_fivetran_log/blob/main/DECISIONLOG.md) | |||
| - Added Quickstart model counts to README. ([#145](https://github.com/fivetran/dbt_fivetran_log/pull/145)) | |||
| - Corrected references to connectors and connections in the README. ([#145](https://github.com/fivetran/dbt_fivetran_log/pull/145)) | |||
| - Updated dbt documentation column and table descriptions for clarity and consistency across models and sources. ([#147](https://github.com/fivetran/dbt_fivetran_log/pull/147)) | |||
There was a problem hiding this comment.
Adding to the current version's changelog as discussed at standup.
4 tasks
4 tasks
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.
PR Overview
This PR will address the following Issue/Feature:
last_successful_sync_completed_atandlast_sync_completed_atfield descriptions and audit all others #146This PR will result in the following new package version:
Overview
Updated these columns for accuracy:
last_sync_completed_atlast_successful_sync_completed_atThe rest of the updates are mainly for consistency and clarity.