GitHub Actions / GitHub Actions

GitHub Actions Secret Not Found on Pull Request Workflows

Fix GitHub Actions workflows failing on pull requests due to repository secrets not being accessible in fork/PR context, while succeeding on direct branch pushes Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 22, 2026 2 sources Needs local verification

Category: GitHub Actions
Error signature: Workflow succeeds on main but fails on PR with 'secret not found' error
Quick fix: Verify the model name, local service connectivity, and network access before retrying the model pull.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Workflow succeeds on main but fails on PR with 'secret not found' error is a GitHub Actions failure pattern reported for developers trying to fix github actions workflows failing on pull requests due to repository secrets not being accessible in fork/pr context, while succeeding on direct branch pushes. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub community discussion #176252 (Oct 2025): Workflow succeeds on main branch but consistently fails on PR with 'secret not found'. This is a well-known security restriction but still causes frequent confusion and production blockers for teams using PR-based CI. Multiple referenced discussions show persistent community struggle. Distinct angle from basic 429/permalink permission errors — focuses on the PR vs main secret accessibility gap. Maps to GitHub Actions.

Common causes

GitHub community discussion #176252 (Oct 2025): Workflow succeeds on main branch but consistently fails on PR with 'secret not found'. This is a well-known security restriction but still causes frequent confusion and production blockers for teams using PR-based CI. Multiple referenced discussions show persistent community struggle. Distinct angle from basic 429/permalink permission errors — focuses on the PR vs main secret accessibility gap. Maps to GitHub Actions.

Quick fixes

Confirm the exact error signature matches Workflow succeeds on main but fails on PR with 'secret not found' error.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Verify the model name, local service connectivity, and network access before retrying the model pull.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Workflow succeeds on main but fails on PR with 'secret not found' error exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Workflow succeeds on main but fails on PR with 'secret not found' error mean in GitHub Actions?

Workflow succeeds on main but fails on PR with 'secret not found' error indicates the workflow described by "GitHub Actions Secret Not Found on Pull Request Workflows" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Workflow succeeds on main but fails on PR with 'secret not found' error?

Check whether this cause matches your environment: GitHub community discussion #176252 (Oct 2025): Workflow succeeds on main branch but consistently fails on PR with 'secret not found'. This is a well-known security restriction but still causes frequent confusion and production blockers for teams using PR-based CI. Multiple referenced discussions show persistent community struggle. Distinct angle from basic 429/permalink permission errors — focuses on the PR vs main secret accessibility gap. Maps to GitHub Actions.

Is the Workflow succeeds on main but fails on PR with 'secret not found' error guidance source-backed?

The "GitHub Actions Secret Not Found on Pull Request Workflows" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Workflow succeeds on main but fails on PR with 'secret not found' error?

For "GitHub Actions Secret Not Found on Pull Request Workflows", avoid applying "Verify the model name, local service connectivity, and network access before retrying the model pull." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Workflow succeeds on main but fails on PR with 'secret not found' error?

For "GitHub Actions Secret Not Found on Pull Request Workflows", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.