Repository navigation
feature/build-issue-label-history-model - #85
Merged
Merged
Conversation
fivetran-jamie
approved these changes
Nov 5, 2026
Contributor
There was a problem hiding this comment.
Looks awesome! Some doc comments that shouldn't block approval
| | [github__weekly_metrics](https://fivetran.github.io/dbt_github/#!/model/model.github.github__weekly_metrics) | Aggregates weekly repository activity to analyze sprint-level productivity, track week-over-week trends, and understand development patterns at the weekly cadence. <br></br>**Example Analytics Questions:**<ul><li>What is the weekly throughput of pull requests and issues by repository?</li><li>How do weekly development metrics trend over time?</li><li>Which weeks show the highest productivity in terms of PRs merged and issues resolved?</li></ul>| | ||
| | [github__monthly_metrics](https://fivetran.github.io/dbt_github/#!/model/model.github.github__monthly_metrics) | Summarizes monthly repository activity to track long-term development trends, measure team productivity over time, and identify seasonal patterns in contribution activity. <br></br>**Example Analytics Questions:**<ul><li>How do monthly pull request and issue volumes trend across repositories?</li><li>What is the month-over-month growth in development activity and code contributions?</li><li>Which months show the highest productivity and how does this align with roadmap milestones?</li></ul>| | ||
| | [github__quarterly_metrics](https://fivetran.github.io/dbt_github/#!/model/model.github.github__quarterly_metrics) | Provides quarterly repository performance metrics to support strategic planning, measure progress against OKRs, and understand high-level development trends by quarter. <br></br>**Example Analytics Questions:**<ul><li>What is the quarterly velocity of feature development and issue resolution by repository?</li><li>How do quarterly metrics align with product roadmap goals and release cycles?</li><li>Which quarters show the strongest team performance and code contribution activity?</li></ul>| | ||
| | [github__issue_label_history](https://fivetran.github.io/dbt_github/#!/model/model.github.github__issue_label_history) | Tracks each period a label is applied to an issue or pull request, including when the label was added and removed and who added and removed it. <br></br>**Example Analytics Questions:**<ul><li>How long do issues typically keep a given label, such as `needs triage` or `blocked`?</li><li>How often is a label removed and re-applied to the same issue?</li><li>Which contributors apply and remove labels most often?</li></ul>| |
Contributor
There was a problem hiding this comment.
Could you update the model count in the README?
Contributor
Author
There was a problem hiding this comment.
Ah, interesting...that wasn't caught by the data model builder. Will open a PR for that.
Comment on lines
+12
to
+16
| - '[stg_github__issue_label_history](https://fivetran.github.io/dbt_github/#!/model/model.github.stg_github__issue_label_history)' | ||
| change_type: New model | ||
| notes: Stages the `ISSUE_LABEL_HISTORY` source table. | ||
| - models: | ||
| - '[stg_github__issue_label_history_tmp](https://fivetran.github.io/dbt_github/#!/model/model.github.stg_github__issue_label_history_tmp)' |
Contributor
There was a problem hiding this comment.
Could probably combine these
Contributor
Author
There was a problem hiding this comment.
Don't they usually get their own entries?
Contributor
Author
There was a problem hiding this comment.
Looks like we're not consistent. Combined them.
| for details. | ||
| - models: | ||
| - '[stg_github__issue_label_history](https://fivetran.github.io/dbt_github/#!/model/model.github.stg_github__issue_label_history)' | ||
| change_type: New model |
Contributor
There was a problem hiding this comment.
Suggested change
| change_type: New model | |
| change_type: New staging model |
| notes: Stages the `ISSUE_LABEL_HISTORY` source table. | ||
| - models: | ||
| - '[stg_github__issue_label_history_tmp](https://fivetran.github.io/dbt_github/#!/model/model.github.stg_github__issue_label_history_tmp)' | ||
| change_type: New model |
Contributor
There was a problem hiding this comment.
Suggested change
| change_type: New model | |
| change_type: New staging model |
Comment on lines
+20
to
+24
| - description: Adds the `github__using_issue_label_history` variable, which defaults | ||
| to `true`. Set it to `false` to disable the new issue label history models if you | ||
| don't sync the `ISSUE_LABEL_HISTORY` table. The models are also disabled when | ||
| `github__using_label` is `false`. See the [README](https://github.com/fivetran/dbt_github/#disable-models-for-non-existent-sources) | ||
| for details. |
Contributor
There was a problem hiding this comment.
Suggested change
| - description: Adds the `github__using_issue_label_history` variable, which defaults | |
| to `true`. Set it to `false` to disable the new issue label history models if you | |
| don't sync the `ISSUE_LABEL_HISTORY` table. The models are also disabled when | |
| `github__using_label` is `false`. See the [README](https://github.com/fivetran/dbt_github/#disable-models-for-non-existent-sources) | |
| for details. | |
| - description: Adds the `github__using_issue_label_history` variable, which is dynamically configured in Quickstart and defaults | |
| to `true` for self-managed dbt projects . Set it to `false` to disable the new issue label history models if you | |
| don't sync the `ISSUE_LABEL_HISTORY` table. The models are also disabled when | |
| `github__using_label` is `false`. See the [README](https://github.com/fivetran/dbt_github/#disable-models-for-non-existent-sources) | |
| for details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Overview
Package version introduced in this PR:
This PR addresses the following Issue/Feature(s):
Summary of changes:
github__issue_label_historyend model, which tracks each period a label is applied to an issue or pull request, including when the label was added and removed and who added and removed it. Disabled by default.stg_github__issue_label_historysource table to the package. Disabled by default.Submission Checklist
Changelog