Fix GitHub Deployment ref for fork PRs#536
Merged
miparnisari merged 1 commit intomainfrom Mar 30, 2026
Merged
Conversation
With pull_request_target the default ref is the base branch, so the fork's branch name doesn't exist in the base repo. Pass the PR head SHA explicitly so the GitHub Deployments API can resolve it. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment status for this pull request.
|
miparnisari
approved these changes
Mar 30, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Summary
No ref found for: <branch>on fork PRsProblem
After #535 switched the Vercel preview workflow to
pull_request_target, thechrnorm/deployment-actionstep fails because it defaults to using the current git ref, which is now the base branch (main). The fork's branch name (e.g.fix/issue-525-crdb-fully-consistent-nuances) doesn't exist in the base repo, so the GitHub Deployments API rejects it.Failing run: https://github.com/authzed/docs/actions/runs/23762650252/job/69233967278
Fix
Pass
ref: ${{ github.event.pull_request.head.sha }}explicitly tochrnorm/deployment-action. The commit SHA is valid regardless of whether the branch exists in the base repo.Test plan
🤖 Generated with Claude Code