Skip to content
This repository was archived by the owner on Jan 20, 2026. It is now read-only.

Correct capitalization of GitHub in README file #43

Merged
fivetran-catfritz merged 2 commits into from
Oct 1, 2025
Merged

Correct capitalization of GitHub in README file #43

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4c6aac
Correct capitalization of GitHub in README file
AK-Fivetran Apr 28, 2025
8419028
Merge branch 'main' into AK-Fivetran-patch-1
fivetran-catfritz Oct 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Github Source dbt Package ([Docs](https://fivetran.github.io/dbt_github_source/))
# GitHub Source dbt Package ([Docs](https://fivetran.github.io/dbt_github_source/))

<p align="left">
<a alt="License"
Expand All @@ -17,19 +17,19 @@

## What does this dbt package do?
<!--section="github_source_model"-->
- Materializes [Github staging tables](https://fivetran.github.io/dbt_github_source/#!/overview/github_source/models/?g_v=1&g_e=seeds) which leverage data in the format described by [this ERD](https://fivetran.com/docs/applications/github/#schemainformation). These staging tables clean, test, and prepare your Github data from [Fivetran's connector](https://fivetran.com/docs/applications/github) for analysis by doing the following:
- Materializes [GitHub staging tables](https://fivetran.github.io/dbt_github_source/#!/overview/github_source/models/?g_v=1&g_e=seeds) which leverage data in the format described by [this ERD](https://fivetran.com/docs/applications/github/#schemainformation). These staging tables clean, test, and prepare your GitHub data from [Fivetran's connector](https://fivetran.com/docs/applications/github) for analysis by doing the following:
- Name columns for consistency across all packages and for easier analysis
- Adds freshness tests to source data
- dbt Core >= 1.9.6 is required to run freshness tests out of the box
- Adds column-level testing where applicable. For example, all primary keys are tested for uniqueness and non-null values.
- Generates a comprehensive data dictionary of your Github data through the [dbt docs site](https://fivetran.github.io/dbt_github_source/).
- These tables are designed to work simultaneously with our [Github transformation package](https://github.com/fivetran/dbt_github).
- Generates a comprehensive data dictionary of your GitHub data through the [dbt docs site](https://fivetran.github.io/dbt_github_source/).
- These tables are designed to work simultaneously with our [GitHub transformation package](https://github.com/fivetran/dbt_github).
<!--section-end-->

## How do I use the dbt package?
### Step 1: Prerequisites
To use this dbt package, you must have the following:
- At least one Fivetran Github connection syncing data into your destination.
- At least one Fivetran GitHub connection syncing data into your destination.
- A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL** or **Databricks** destination.

#### Databricks Dispatch Configuration
Expand Down Expand Up @@ -59,7 +59,7 @@ 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.
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 `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:

Expand Down
Loading