mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2500] Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable but succeeds with github actions #1158
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1158
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @noamzilo on GitHub (Oct 22, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2500
Bug report info
Command used with act
Describe issue
Expecting success just like github actions
Link to GitHub repository
https://github.com/noamzilo/personal_website
Workflow content
Relevant log output
Additional information
The workflow is fine, as github actions does succeed, so clearly this is a problem with act.
My .secrets file contains:
and I checked all env variables and secrets get passed correctly into the build.
I read some answers and implemented them, but no luck.
Would appreciate help, because having to push for debugging really sucks.
@github-actions[bot] commented on GitHub (Apr 21, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@noamzilo commented on GitHub (Apr 21, 2025):
Not stale
@smoglica commented on GitHub (Jul 16, 2025):
The
actions/deploy-pagesrequires theid-token: write(Token to request an OpenID Connect token) permission to be granted toGITHUB_TOKEN. You're already doing this in thebuild-and-deployjob.You cannot set the
id-token: writepermission on a Personal Access Token (PAT). Theid-tokenpermission is specific to GitHub Actions' built-inGITHUB_TOKENand is used for OpenID Connect (OIDC) federation GitHub Actions and cloud providers.When running workflows locally with act, OIDC (id-token) is not supported, because act cannot mint or sign OIDC tokens like GitHub Actions does.
Seems that feature is planned to be handled. You can check in Unsupported functionality page