Thanks for the response @martinmalek!

I just finished adding the team and repo_team tables to the source package, and added the teams aggregate field (repository_team_names) to the github__issue and github__pull_request models. This way you will be able to have team visibility in the final models! Would you be willing to install the mentioned working branch of the transform package and let me know if the results look accurate on your end?

Please be aware this working branch also includes renaming source and transform models to be consistent with our current naming standard. As such, if you install and run this working branch it will create new tables in your warehouse (for example github_issues has now been changed to github__issues and thus will create a new table when executed). If you are willing to test, you can change your packages.yml file to reference the following:

  - git: https://github.com/fivetran/dbt_github.git
    revision: joe-feature-updates
    warn-unpinned: false

Once you have updated your packages.yml file you may execute the below to to remove old package dependencies and install the working branch

dbt clean && dbt deps

Finally you can then execute dbt run.

Let me know if the results are what you expect and I can open this branch up for a PR to master.

Thanks again!

Add Team support #70

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions