Are you a current Fivetran customer?

Fivetran created PR

What change(s) does this PR introduce?

This PR apply changes that are a result of the upstream modifications within the source package. The addition of the label table, and depreciation of the label field within the issue_label table resulted in a number of updates needing to be applied. In particular, the creation of the int_github__issue_label_join model is the main update to account for these upstream changes.

Additionally, this PR fixes some out of date procedures. For example, references to staging models has been changed to vars for a more dynamic use of the package.

Finally, I noticed the int_github__issue_comment model was using the stg_github__issue_label model to generate the total count of comments. This is not accurate and has been adjusted to reference the stg_github__issue_comment model.

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide explanation how the change is non breaking below.)

Due to the upstream changes, this will result in a breaking change.

Is this PR in response to a previously created Issue

• Yes, Issue #21
• No

How did you test the PR changes?

• CircleCi
• Other (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• Snowflake
• Postgres
• Databricks
• Other (provide details below)

Provide an emoji that best describes your current mood

🏷️

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.