mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #678] Issue: Checkout fails on 0.2.22 - "Input required and not supplied: token" #433
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#433
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 @Lexmark-peachj on GitHub (May 7, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/678
Originally assigned to: @catthehacker on GitHub.
Act version
Expected behaviour
The checkout action's behavior is different between 0.2.21 and 0.22.22. In 0.2.21, checkout seemed to
docker cpthe repository into the image rather than perform an actual checkout. This was desirable because local changes to actions and associated scripts were properly consumed without having to push them to the repository.Actual behaviour
act 0.2.22 actually checks out the repo. This has two immediate downsides:
Workflow and/or repository
My checkout action was this:
actoutputLog
Note: I'm new to using act and GitHub Actions, so please let me know if I should do something differently in my workflow.
@catthehacker commented on GitHub (May 7, 2021):
Broken as of
github.com/nektos/act@0f049426f6@catthehacker commented on GitHub (May 7, 2021):
cc @JustinGrote
@JustinGrote commented on GitHub (May 8, 2021):
Spotted and fixed as part of another, I'll hot fix this real quick.
@catthehacker commented on GitHub (May 8, 2021):
I told you we did not need
GITHUB_TOKENbefore 😋@JustinGrote commented on GitHub (May 8, 2021):
I actually broke this indirectly, this != should be ==
github.com/nektos/act@0f049426f6 (diff-c057d66dc9)@JustinGrote commented on GitHub (May 10, 2021):
@Lexmark-peachj can you test this build and see if it fixes your use case?
https://github.com/nektos/act/suites/2686549445/artifacts/59224642
@Lexmark-peachj commented on GitHub (May 11, 2021):
Works great, thanks for your help!
@cyc115 commented on GitHub (May 18, 2021):
Hi there! Can there be a minor release for this?
@catthehacker commented on GitHub (May 18, 2021):
@cplee
@bixu commented on GitHub (May 19, 2021):
I concur with @cyc115 -- my teams love Act, but we've had to pause using it until this fix gets released.
@catthehacker commented on GitHub (May 19, 2021):
You can always get snapshot build https://github.com/nektos/act/pull/680/checks?check_run_id=2535655295

@bixu commented on GitHub (May 19, 2021):
@catthehacker, good call!
Is it possible to do this with Brew? I can use the snapshot build personally but will have a hard time propagating this across team workflows :)
@catthehacker commented on GitHub (May 19, 2021):
I think it's not possible to get build at specific commit, but correct me if I'm wrong. I've used
brewjust couple times in my life.@nathanagez commented on GitHub (May 28, 2021):
Same issue, installed via brew
@akrabat commented on GitHub (May 28, 2021):
Will installing act using
curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bashresult in a version that has this fix?@catthehacker commented on GitHub (May 28, 2021):
Unfortunately it will not.
@akrabat commented on GitHub (May 28, 2021):
Thanks.
Update: On Mac, just do
brew unlink act && brew install act --HEADas per https://github.com/nektos/act/issues/678#issuecomment-850466260So, the way to get the snapshot to work on Mac appears to be:1. Go to https://github.com/nektos/act/pull/680/checks?check_run_id=2535655295 and click on the "Artifacts" dropdown on the right.2. Click on act-macos to download the zip file containing the binary3. unzip act-macos.zip to create a file callact4. In a Terminal, navigate to where you unzipped act-macos.zip and add executable permissions to theactfile typing:chmod a+x act5. Bypass MacOS gatekeeper by typingopen act. This will open a Terminal window. Close it when it says "[Process completed]".6. Moveactto a directory on your path. e.g.mv act /usr/local/binWhen the next version of act is released, deleteusr/local/bin/actand then install the new version.@catthehacker commented on GitHub (May 28, 2021):
That's correct, other option is you can install previous version of
actwhich doesn't have that issue.@TonalidadeHidrica commented on GitHub (May 28, 2021):
This info is outdated.
Actually there's a better way for `brew`.brew edit act. It will open a file namedact.rb, so add the following lines:brew unlink actandbrew install --HEAD act. You've got a fixed latest version! Hooray!@TonalidadeHidrica commented on GitHub (May 28, 2021):
I updated the Homebrew formula, so now the HEAD version is available via
brew install act --HEAD(afterbrew updateand maybebrew unlink act).@catthehacker commented on GitHub (May 28, 2021):
cc @akrabat @nathanagez @bixu
@akrabat commented on GitHub (May 28, 2021):
Fantastic. Thanks @TonalidadeHidrica!
@notmatthancock commented on GitHub (Jun 2, 2021):
I'm on Ubuntu 20.04. I downloaded the Linux tar.gz for the previous release of v0.2.20 here. After unzipping and extracting the
actexecutable from the tar.gz file, I'm able to execute the examples in the demo repo without the error described in this issue.@saniales commented on GitHub (Jun 4, 2021):
Still not working on my side (v 0.2.22)
@TonalidadeHidrica commented on GitHub (Jun 4, 2021):
@saniales
v0.2.22does not include the fix made 25 days ago, since it was released 29 days ago. You have to install manually the latest build onmasterbranch, which you can obtain by the several ways described above.@catthehacker commented on GitHub (Jun 4, 2021):
Or you can get binary from artefacts in https://github.com/nektos/act/pull/680
@saniales commented on GitHub (Jun 4, 2021):
ATM i am ok is using v 0.2.20 version, which works, but thank you <3
@marnix commented on GitHub (Jun 5, 2021):
For anyone interested, I observed this as well, using 0.2.22 via Nix on Ubuntu. Found out how to install 0.2.21 via https://lazamar.co.uk/nix-versions/?package=act&version=0.2.21&fullName=act-0.2.21&keyName=act&revision=c92ca95afb5043bc6faa0d526460584eccff2277&channel=nixpkgs-unstable#instructions , that resolved this issue for me.
@JustinGrote commented on GitHub (Jun 5, 2021):
@marnix you can also just download the prerelease artifact from the PR: https://github.com/nektos/act/suites/2686549445/artifacts/59224642
@righel commented on GitHub (Jun 9, 2021):
If I add the "with:" property I have the same token error, if I remove it works ok (using the latest version).
sample:
output:
@catthehacker commented on GitHub (Jun 9, 2021):
@righel because then you want to checkout specific version instead of what you have in your workdir so you need token
@catthehacker commented on GitHub (Jun 11, 2021):
v0.2.23has been released that includes fix for this issue.@lucasdemarchi commented on GitHub (Jul 1, 2021):
Just tested master branch with
github.com/git-pile/playground@f2e5a12a83and it seems broken for me:Note that in that workflow it's trying to checkout a specific branch of another (public) repository
@Siddharth-Ashri commented on GitHub (Jul 2, 2021):
Trying it locally gives it the same error as above repo is private though
@lucasdemarchi commented on GitHub (Jul 6, 2021):
@Siddharth-Ashri repo I'm referencing is not private
@FrancescoSaverioZuppichini commented on GitHub (Oct 6, 2021):
same error here
@catthehacker commented on GitHub (Oct 7, 2021):
if you checkout specific branch/commit/etc. token is required no matter if it's private or not
works for everyone else
@francisco-gs-colpal commented on GitHub (Oct 19, 2021):
I had the same problem but running the workflow in dry mode and passing github token it works
I read it from here https://github.com/nektos/act/issues/779#issuecomment-932997696
@epignatelli commented on GitHub (Sep 13, 2022):
Dryrun only checks for correctness (https://github.com/nektos/act/issues/268#issuecomment-1056000096), it does not run the workflow.
@epignatelli commented on GitHub (Sep 13, 2022):
How is this solved?
This issue should be re-opened.
@till commented on GitHub (Nov 20, 2022):
@epignatelli did you manage to resolve this, or do you still have that problem?
I have this in my steps:
Yields:
Maybe it changed with
v3to require this always? I guess for completeness, I am cloning inside a workflow run of a private repository. The initial clone works, but this one doesn't. Also tried setting an empty token to no avail.@zhongweiy commented on GitHub (Aug 25, 2023):
I'm on version
act version 0.2.34and usingactions/checkout@v2on a public repo. The error still exists.The workaround is replacing
uses: actions/checkout@v2with a pure git clonerun: git clone https://github.com/example/example.git, like this commit. It is inconvenient if you need to do other things bycheckout@v2, you have to do it manually by shell commands.