-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated test for stg_qualtrics__distribution_contact
#9
Conversation
Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
Distribution contact test
stg_qualtrics__distribution_contact
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-avinash left a couple suggestions!
CHANGELOG.md
Outdated
@@ -1,3 +1,12 @@ | |||
# v0.2.2 dbt_qualtrics_source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# v0.2.2 dbt_qualtrics_source | |
# dbt_qualtrics_source v0.2.2 |
Updating for compatibility with the auto releaser.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
CHANGELOG.md
Outdated
- Updated unique combination of columns test on `stg_qualtrics__distribution_contact` to include `contact_lookup_id`. [PR #8](https://github.com/fivetran/dbt_qualtrics_source/pull/8) | ||
|
||
## Contributors | ||
- [@dmcmtntp](https://github.com/dmcmtntp) [PR #8](https://github.com/fivetran/dbt_qualtrics_source/pull/8) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [@dmcmtntp](https://github.com/dmcmtntp) [PR #8](https://github.com/fivetran/dbt_qualtrics_source/pull/8) | |
- [@dmcmtntp](https://github.com/dmcmtntp) ([PR #8](https://github.com/fivetran/dbt_qualtrics_source/pull/8)) |
Tiny formatting suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formattnig applied
CHANGELOG.md
Outdated
[PR #9](https://github.com/fivetran/dbt_qualtrics_source/pull/9) includes the following updates: | ||
|
||
## Bug Fix | ||
- Updated unique combination of columns test on `stg_qualtrics__distribution_contact` to include `contact_lookup_id`. [PR #8](https://github.com/fivetran/dbt_qualtrics_source/pull/8) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a reason why it had to be added (was it accidentally omitted or was there a connector update, etc?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-catfritz Changes applied!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm for release!
PR Overview
This PR will address the following Issue/Feature: [#7]
This PR will result in the following new package version: v0.2.2
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fix
stg_qualtrics__distribution_contact
to includecontact_lookup_id
. PR #8PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
Customer was able to validate that the new test didn't fail.
If you had to summarize this PR in an emoji, which would it be?
🤝