mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #778] Issue: Github action checkout tries to checkout old repo and doesn't follow redirects #486
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#486
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 @krasi-georgiev on GitHub (Aug 17, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/778
Originally assigned to: @catthehacker on GitHub.
System information
Actual behavior
The Repo has a redirect and the checkout step tries to checkout the old repo without following the redirect. The same workflow works when in github actions
https://github.com/brocaar/chirpstack-application-server/runs/3350138619?check_suite_focus=true
Workflow and/or repository
https://github.com/brocaar/chirpstack-application-server/runs/3350138619?check_suite_focus=true
Steps to reproduce
act -j docker -v -e .local/gh-event.json
actoutputLog
Event file@catthehacker commented on GitHub (Aug 17, 2021):
That seems to be rather local issue or with Docker compose. Can you paste output of
.git/config?@krasi-georgiev commented on GitHub (Aug 17, 2021):
yes you are right, still fails, but I think that this is because the GITHUB_TOKEN doesn't have permission to clone this repo which is weird since it is a public repo.
This is the updated git config
@catthehacker commented on GitHub (Aug 17, 2021):
GITHUB_TOKENis always required when cloning.@krasi-georgiev commented on GitHub (Aug 17, 2021):
yep, I see it in the docs, this is not my repo so the token can't have access to that repo so now trying to figure out how to use local cloning instead of remote.
@catthehacker commented on GitHub (Aug 17, 2021):
supplying your own token should work, the token does not need to have access to specific repo, it's only for the API to understand what it needs to clone so
repo>public_repoPAT should work fine@krasi-georgiev commented on GitHub (Aug 17, 2021):
hhm, strange I already had the token in the
.secretsfile with the right permissions, but still getting@catthehacker commented on GitHub (Aug 17, 2021):
Since it comes from BuildKit I'm unsure what happens here exactly