mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #427] Checks out too much of the git repository #297
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#297
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 @mosesn on GitHub (Nov 20, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/427
I was debugging a problem where we were seeing "unrelated file histories" on a github action. The root of the problem ended up being that we were using
git fetch --depth=1and should not have been specifying a depth. However, when I tried to reproduce the problem with nektos/act, I was unable to. Tbh why this failed is still somewhat mysterious to me, but it does seem to be a discrepancy between how github actions works and how nektos/act works.This is the problematic line:
github.com/twitter/dodo@c89e28eb0d/.github/workflows/merge.yml (L23)And here is the failing github action:
https://github.com/twitter/dodo/runs/1409487703?check_suite_focus=true#step:3:9
@github-actions[bot] commented on GitHub (Jan 16, 2021):
Issue is stale and will be closed in 14 days unless there is new activity