mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #428] If the local checkout is a submodule, in-container git commands don't work #295
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#295
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 @obra on GitHub (Nov 20, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/428
Hi!
I noticed that some of the jobs I have that work just great in production with GitHub actions fail in act.
I've tracked the problem down to the fact that when act copies the toplevel repository into the docker vms, it makes a verbatim copy, rather than a git clone.
In most situations, this is just fine. In my situation, however, the repo is typically checked out as a submodule of another repo, which means that .git is a file with the path of the git dir in the parent's .git.
Some of my actions rely on 'git ls-files', which can't work in the absence of the actual git directory.
@github-actions[bot] commented on GitHub (Jan 16, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@amlcodes commented on GitHub (Aug 4, 2022):
bump
needsjob output #1528