🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_github_source. Additionally, the latest dbt_github_source package has a dependency on the latest dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Happy Friday! 🥳

This release addresses issue #17, in which the package failed if you do not have the repo_team source table synced.

If you would like to disable all tables and logic related to repo_team, set the github__using_repo_team variable to false in your dbt_project.yml file.

This release contains the following non-breaking changes:

• Update to the packages.yml file to reference any current non-breaking source package releases.

🚨This update introduces a breaking change: Output models are renamed to include a double underscore between the source name and the table name. For example, github_issue.sql is now github__issue.sql. 🚨

The release also:

• Compatibility with dbt v0.19.0
• Introduces CircleCI testing
• Introduces the repository_team_names field within the github__issues and github__pull_requests models to allow for teams visibility.
• Works with the latest version of the Github source package v0.2.1.

This release does 2 things:

1. Fixes bug in github_pull_request_times which was causing spreading -- pull_request_id & issue_id were not unique.
2. Moves macro logic to dbt_fivetran_utils. This is our repo which will include all macros going forward.

Updates package to be compatible with dbt 0.18.0. This is a breaking change!
🚨 dbt v0.18.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package

This is the initial release of this package.

This package enables you to better understand your GitHub issues and pull requests. The main focus is to enhance these two core objects with commonly used metrics. Additionally, the metrics tables allow you to better understand your team's velocity over time. These metrics are available on a daily, weekly, monthly and quarterly level.

Currently the package supports Redshift, BigQuery and Snowflake.