Add disabling variables for issue_assignee, issue_label, label, and requested_reviewer_history (#64)

* working

* tests

* tweaks

* docs

* joe feedback

* avinash feedback

* switch source package dep

Author: fivetran-jamie

.buildkite/scripts/run_models.sh

@@ -18,9 +18,9 @@ cd integration_tests
 dbt deps
 dbt seed --target "$db" --full-refresh
 dbt source freshness --target "$db" || echo "...Only verifying freshness runs…"
+dbt run --vars '{github__using_repo_team: false, github__using_issue_assignee: false, github__using_issue_label: false, github__using_requested_reviewer_history: false, github__using_label: false}' --target "$db" --full-refresh
+dbt test --vars '{github__using_repo_team: false, github__using_issue_assignee: false, github__using_issue_label: false, github__using_requested_reviewer_history: false, github__using_label: false}' --target "$db"
 dbt run --target "$db" --full-refresh
 dbt test --target "$db"
-dbt run --vars '{github__using_repo_team: false}' --target "$db" --full-refresh
-dbt test --target "$db"
 
 dbt run-operation fivetran_utils.drop_schemas_automation --target "$db"

.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md

@@ -1,29 +1,35 @@
-## PR Overview
-**This PR will address the following Issue/Feature:**
+<!--
+Pre-Submission Reminders  
+Before marking this PR as "ready for review":
 
-**This PR will result in the following new package version:**
-<!--- Please add details around your decision for breaking vs non-breaking version upgrade. If this is a breaking change, were backwards-compatible options explored? -->
+- `dbt run --full-refresh && dbt test`  
+- `dbt run` && `dbt test` (if incremental models are present)  
+- The related issue is linked, tagged, and appropriately assigned  
+- Documentation and version updates are included, if applicable  
+- `docs` have been regenerated (unless there are no code or YAML changes)  
+- BuildKite integration tests are passing
+-->
 
-**Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:**
-<!--- Copy/paste the CHANGELOG for this version below. -->
+## PR Overview 
+**Package version introduced in this PR:** 
+ 
+**This PR addresses the following Issue/Feature(s):**
+<!-- Add Issue # or internal ticket reference -->
 
-## PR Checklist
-### Basic Validation
-Please acknowledge that you have successfully performed the following commands locally:
-- [ ] dbt run –full-refresh && dbt test
-- [ ] dbt run (if incremental models are present) && dbt test
+**Summary of changes:**  
+<!-- 1-2 sentences describing PR changes. -->
 
-Before marking this PR as "ready for review" the following have been applied:
-- [ ] The appropriate issue has been linked, tagged, and properly assigned
-- [ ] All necessary documentation and version upgrades have been applied
-- [ ] docs were regenerated (unless this PR does not include any code or yml updates)
-- [ ] BuildKite integration tests are passing
-- [ ] Detailed validation steps have been provided below
 
-### Detailed Validation
-Please share any and all of your validation steps:
-<!--- Provide the steps you took to validate your changes below. -->
+### Submission Checklist  
+- [ ] Alignment meeting with the reviewer (if needed)  
+  - [ ] Timeline and validation requirements discussed  
+- [ ] Provide validation details:  
+  - [ ] **Validation Steps:** Check for unintentional effects (e.g., add/run consistency & integrity tests)
+  - [ ] **Testing Instructions:** Confirm the change addresses the issue(s)
+  - [ ] **Focus Areas:** Complex logic or queries that need extra attention  
 
-### If you had to summarize this PR in an emoji, which would it be?
-<!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908)  --> 
-:dancer:
+### Changelog  
+<!-- Recommend drafting changelog notes, then refining via ChatGPT using:  
+"Draft a changelog entry based on the following notes." -->
+- [ ] Draft changelog for PR  
+- [ ] Final changelog for release review

.quickstart/quickstart.yml

@@ -4,9 +4,17 @@ schema_key: github_schema
 dbt_versions: ">=1.3.0 <2.0.0"
 
 table_variables:
+  github__using_issue_assignee:
+    - issue_assignee
+  github__using_issue_label:
+    - issue_label
+  github__using_label:
+    - label
   github__using_repo_team:
     - repo_team
     - team
+  github__using_requested_reviewer_history:
+    - requested_reviewer_history
 
 destination_configurations:
   databricks:

CHANGELOG.md

@@ -1,3 +1,19 @@
+# dbt_github v0.9.1
+
+[PR #64](https://github.com/fivetran/dbt_github/pull/64) includes the following updates:
+
+## Feature Updates
+- Added the following variables to account for potentially missing tables. For dbt Core users, each is `True` by default and will need to be set to `False` in the root project's `dbt_project.yml`. For Fivetran Quickstart users, they will be dynamically enabled/disabled based on the presence of the associated source table.
+  - `github__using_issue_assignee`: Disable if missing `ISSUE_ASSIGNEE`
+  - `github__using_issue_label`: Disable if missing `ISSUE_LABEL`
+  - `github__using_label`: Disable if missing `LABEL`
+  - `github__using_requested_reviewer_history`: Disable if missing `REQUESTED_REVIEWER_HISTORY`
+
+## Under the Hood
+- Updated package maintainer PR template.
+- Added new variables to the `quickstart.yml` file.
+- Added consistency validation tests for the `github__daily/weeky/monthly/quarterly_metrics` models.
+
 # dbt_github v0.9.0
 
 [PR #63](https://github.com/fivetran/dbt_github/pull/63) includes the following updates:

LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright © 2025 Fivetran Inc.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

README.md

@@ -1,4 +1,6 @@
-<p align="center">
+# Github dbt Package ([Docs](https://fivetran.github.io/dbt_github/))
+
+<p align="left">
     <a alt="License"
         href="https://github.com/fivetran/dbt_github/blob/main/LICENSE">
         <img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" /></a>
@@ -13,7 +15,6 @@
         <img src="https://img.shields.io/badge/Fivetran_Quickstart_Compatible%3F-yes-green.svg" /></a>
 </p>
 
-# Github dbt Package ([Docs](https://fivetran.github.io/dbt_github/))
 ## What does this dbt package do?
 
 - Produces modeled tables that leverage Github data from [Fivetran's connector](https://fivetran.com/docs/applications/github) in the format described by [this ERD](https://fivetran.com/docs/applications/github#schemainformation) and builds off of the output from our [github source package](https://github.com/fivetran/dbt_github_source).
@@ -80,14 +81,18 @@ vars:
 ### Step 4: Disable models for non-existent sources
 Your Github connection might not sync every table that this package expects. If your syncs exclude certain tables, it is because you either don't use that functionality in Github or have actively excluded some tables from your syncs.
 
-If you do not have the `REPO_TEAM` table synced, add the following variable to your `dbt_project.yml` file:
+If you do not have the `TEAM`, `REPO_TEAM`, `ISSUE_ASSIGNEE`, `ISSUE_LABEL`, `LABEL`, or `REQUESTED_REVIEWER_HISTORY` tables synced and are not running the package via Fivetran Quickstart, add the following variables to your `dbt_project.yml` file:
 
 ```yml
 vars:
-    github__using_repo_team: false # by default this is assumed to be true
+    github__using_repo_team: false # by default this is assumed to be true. Set to false if missing TEAM or REPO_TEAM
+    github__using_issue_assignee: false # by default this is assumed to be true
+    github__using_issue_label: false # by default this is assumed to be true
+    github__using_label: false # by default this is assumed to be true
+    github__using_requested_reviewer_history: false # by default this is assumed to be true
 ```
 
-*Note: This package only integrates the above variable. If you'd like to disable other models, please create an [issue](https://github.com/fivetran/dbt_github/issues) specifying which ones.*
+*Note: This package only integrates the above variables. If you'd like to disable other models, please create an [issue](https://github.com/fivetran/dbt_github/issues) specifying which ones.*
 
 ### (Optional) Step 5: Additional configurations
 

dbt_project.yml

@@ -1,6 +1,6 @@
 config-version: 2
 name: 'github'
-version: '0.9.0'
+version: '0.9.1'
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 models:
   github: