mirror of
https://github.com/nektos/act.git
synced 2026-04-27 01:45:52 +03:00
[GH-ISSUE #2197] act favors secrets from .secrets over values from -s #1037
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#1037
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 @jsoref on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2197
Bug report info
Command used with act
Describe issue
Using a fine-grained token that allows contents:read for a private repository, act (using
--use-new-action-cache) isn't able to retrieve my public action.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
https://github.com/settings/tokens?type=beta
https://docs.github.com/en/rest/authentication/permissions-required-for-fine-grained-personal-access-tokens?apiVersion=2022-11-28
Apparently I have an expired GITHUB_TOKEN in
.secretswhich has precedence over the-s GITHUB_TOKEN=.... This is undesirable.@ChristopherHX commented on GitHub (Feb 2, 2024):
Weird I have just created a fine grained PAT.
With almost no access, but
- uses: actions/cache@refs/heads/mainand other public actions didn't break for meDoes act use the correct GITHUB_TOKEN?
Using
- uses: christopherhx/ghat3@testworks, access denied for youUsing
- uses: christopherhx/ghat2@testaccess denied, but expecedUsing a
.secretsfile with contentBTW: I don't care about leaking these private repo names.
@ChristopherHX commented on GitHub (Feb 2, 2024):
A
.secretsfile with an invalid GITHUB_TOKEN secret seem to override the GITHUB_TOKEN passed from the cli.Is that the bug you are seeing?
@jsoref commented on GitHub (Feb 2, 2024):
You're right, there was an expired token in
.secrets.Sorry.