Snowflake Git Integration: Version-Control SQL Scripts and Notebooks

Snowflake Git Integration registers a Git repository (GitHub, GitLab, etc.) as a Snowflake database object, letting you directly reference and execute the SQL scripts, Python files, and configuration files it contains from inside Snowflake. It's a great fit for Infrastructure as Code (IaC) and CI/CD pipeline integration, and you can also use it to version-control Snowflake Notebooks.

Git Integration Setup Flow

Step 1: Secret（認証情報）の作成
  ↓
Step 2: API Integration（Git API接続）の作成
  ↓
Step 3: Git Repositoryオブジェクトの作成
  ↓
Step 4: FETCH でリモートと同期
  ↓
Step 5: ファイル参照・スクリプト実行

Step 1: Create the authentication Secret

-- GitHubのPersonal Access Token (PAT) を格納
CREATE OR REPLACE SECRET git_pat_secret
  TYPE = PASSWORD
  USERNAME = 'github-username'
  PASSWORD = 'ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx';

-- パブリックリポジトリの場合はSecretは不要

Step 2: Create the API Integration

-- GitHub用のAPI Integration
CREATE OR REPLACE API INTEGRATION github_api_integration
  API_PROVIDER = git_https_api
  API_ALLOWED_PREFIXES = ('https://github.com/my-org/')
  ALLOWED_AUTHENTICATION_SECRETS = (git_pat_secret)
  ENABLED = TRUE;

Step 3: Create the Git Repository

-- Git Repositoryオブジェクトの作成
CREATE OR REPLACE GIT REPOSITORY analytics_db.public.my_sql_repo
  API_INTEGRATION = github_api_integration
  GIT_CREDENTIALS = git_pat_secret
  ORIGIN = 'https://github.com/my-org/snowflake-sql-scripts.git';

-- パブリックリポジトリの場合（認証なし）
CREATE OR REPLACE GIT REPOSITORY analytics_db.public.public_repo
  API_INTEGRATION = github_api_integration
  ORIGIN = 'https://github.com/my-org/public-scripts.git';

Step 4: Fetch from the remote repository

-- リモートリポジトリの最新を取得
ALTER GIT REPOSITORY analytics_db.public.my_sql_repo FETCH;

-- ブランチ一覧を確認
SHOW GIT BRANCHES IN analytics_db.public.my_sql_repo;

-- タグ一覧を確認
SHOW GIT TAGS IN analytics_db.public.my_sql_repo;

Browsing Files

-- mainブランチのファイル一覧
LIST @analytics_db.public.my_sql_repo/branches/main/;

-- 特定ディレクトリのファイル一覧
LIST @analytics_db.public.my_sql_repo/branches/main/sql/transforms/;

-- 特定タグのファイル一覧
LIST @analytics_db.public.my_sql_repo/tags/v1.2.0/;

-- ファイルの内容を読み取り
SELECT $1 AS content
FROM @analytics_db.public.my_sql_repo/branches/main/README.md
(FILE_FORMAT => 'util_db.formats.text_raw');

Executing SQL Scripts

-- Git Repository内のSQLスクリプトを直接実行
EXECUTE IMMEDIATE FROM
  @analytics_db.public.my_sql_repo/branches/main/sql/create_tables.sql;

-- 特定タグ（バージョン）のスクリプトを実行
EXECUTE IMMEDIATE FROM
  @analytics_db.public.my_sql_repo/tags/v1.2.0/sql/migrations/001_add_columns.sql;

-- 変数を渡してスクリプトを実行
EXECUTE IMMEDIATE FROM
  @analytics_db.public.my_sql_repo/branches/main/sql/parameterized_query.sql
  USING (target_date => '2026-03-27', batch_size => 10000);

Git Repository Path Structure

Integration with Snowflake Notebooks

By linking a Snowsight Notebook to a Git repository, the Notebook's versions are managed through Git.

• Connect a Git repository to a Notebook from the Snowsight UI
• Switch branches, commit, and push directly from the UI
• Multiple data scientists can collaborate on the same Notebook through branches
• Run pull-request-based review workflows on GitHub or GitLab

CI/CD Pipeline Pattern

-- TaskでFETCH → スクリプト実行を自動化
CREATE OR REPLACE TASK daily_deploy
  WAREHOUSE = ops_wh
  SCHEDULE = 'USING CRON 0 6 * * * UTC'
AS
  BEGIN
    ALTER GIT REPOSITORY my_sql_repo FETCH;
    EXECUTE IMMEDIATE FROM
      @my_sql_repo/branches/main/sql/daily_etl.sql;
  END;

ALTER TASK daily_deploy RESUME;

Required Privileges

Best Practices

• Tag-based deployments: in production, reference tags rather than branches so you execute a known, pinned version of the script.
• Schedule periodic FETCH with a Task: run FETCH on a schedule via a Task so manual fetches don't get missed.
• Tighten API_ALLOWED_PREFIXES: narrow the API Integration's API_ALLOWED_PREFIXES to the smallest set of repositories you actually need.
• Rotate Secrets: set an expiration on Personal Access Tokens and rotate the Secret on a regular cadence.

Check Your Understanding

Frequently Asked Questions