Skip to content

fix: enable Fusion workflow for fork PRs#563

Merged
b-per merged 1 commit into
mainfrom
fix/fusion-workflow-fork-prs
Feb 3, 2026
Merged

fix: enable Fusion workflow for fork PRs#563
b-per merged 1 commit into
mainfrom
fix/fusion-workflow-fork-prs

Conversation

@b-per
Copy link
Copy Markdown
Collaborator

@b-per b-per commented Feb 3, 2026

Summary

  • Change Fusion workflow from pull_request to pull_request_target so fork PRs have access to repository variables
  • Explicitly checkout the PR head ref (required for pull_request_target)

Problem

Fork PRs (like #525) fail the Fusion integration tests because pull_request event doesn't have access to repository variables (vars.SNOWFLAKE_DATABASE, etc.), resulting in:

error: dbt1005: database is required for snowflake relation

Solution

Use pull_request_target instead, which is the same approach already used by ci.yml for Package Integration Tests. Maintainer approval is required before workflows run on fork PRs.

Change from `pull_request` to `pull_request_target` so that fork PRs
have access to repository variables (like SNOWFLAKE_DATABASE).

This aligns with how ci.yml handles fork PRs. The workflow definition
still comes from the base branch for security, and we explicitly
checkout the PR head for testing.
@b-per b-per requested review from a team, dave-connors-3 and graciegoheen as code owners February 3, 2026 14:57
@b-per b-per merged commit 7333c0c into main Feb 3, 2026
8 of 9 checks passed
@b-per b-per deleted the fix/fusion-workflow-fork-prs branch February 3, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant