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.