mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #568] Issue: #383
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#383
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 @Disturbing on GitHub (Mar 17, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/568
Act version
act version 0.2.20
Expected behaviour
When running an act, I expect all repo files to be there when actions/checkout is ran
Actual behaviour
Some files are missing for some reason.
Workflow and/or repository
C
Cannot share the repo as it's private. But there a 755 bash file called hermit in ./bin in the repo. It does not exist when running on act, but exists on github.com
Steps to reproduce
actoutput[ci/cd/ci ] ⭐ Run cd ./bin && ls
| README.hermit.md aws go golangci-lint hermit.hcl protoc
| activate-hermit aws_completer gofmt goreleaser make
[ci/cd/ci ] ✅ Success - cd ./bin && ls
[ci/cd/ci ] ⭐ Run ./bin/hermit env >> $GITHUB_ENV
| /github/workflow/4: line 1: ./bin/hermit: No such file or directory
[ci/cd/ci ] ❌ Failure - ./bin/hermit env >> $GITHUB_ENV
@Disturbing commented on GitHub (Mar 17, 2021):
If i use --bind it works fine.
@jsoref commented on GitHub (Apr 4, 2021):
@github-actions[bot] commented on GitHub (May 5, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@Disturbing commented on GitHub (May 6, 2021):
i think act was not shutdown correctly and was attaching itself to an old directory after i used --bind once. I'll share more if i figure out how to repo it, but at the moment i deleted the mounted directories / storage in docker and it resolved my issue.