mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #49] empty git-upload-pack given #27
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#27
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 @paulbellamy on GitHub (Mar 11, 2019).
Original GitHub issue: https://github.com/nektos/act/issues/49
As of this afternoon, when running the example gcloud auth workflow (https://github.com/actions/gcloud/tree/master/auth#example-workflow-file), with the errors fixed, I get an error about not being able to clone the repo. Maybe a temporary github error?
The first 2 errors are because it is not a real repo, just a minimal test-case directory I created.
Attached is a tarball of a failing repo. Any info would be super helpful, thanks! Love the project, btw.
act-test.tar.gz
@paulbellamy commented on GitHub (Mar 12, 2019):
Based on a bit more digging (and running
act -v), it seems like the cached clone dir in/var/folders/dn/nkfvgz8n0k51lptgh1m8jfnw0000gn/T/act/actions/gcloud/auth@master/, was corrupt. I removed that folder, re-ran act, and now it worked.My only hypothesis is that the clone died, errored, or got ctrl-c-ed partway through,
leaving the cloned dir present, but empty.
I've attached a tarball of the corrupt clone dir, in case it's useful.
auth@master.tar.gz
@maxheld83 commented on GitHub (Jun 8, 2019):
ran into the same problem; same solution worked.
@cplee commented on GitHub (Feb 25, 2020):
As of version
0.2.2, tempdir is replaced with docker volumes