starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #1042] Issue: actions/checkout@v2 with lfs: true doesn't get file #606

New issue

Open

opened 2026-03-01 21:44:54 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 21:44:54 +03:00

Owner

Originally created by @davetapley on GitHub (Mar 14, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1042

I will fill this out more later but wanted to get a placeholder in, apologies.

I have

      - name: Checkout code
        uses: actions/checkout@v2
        with:
          lfs: true

When pushing to GitHub and running on Actions it gets file:

-rw-r--r--  1 runner docker 185M Mar 14 21:27 dependencies.tar

But when running with act it doesn't get the file (and so tar fails):

| -rw-rw-rw-  1 1000 root  134 Aug 24  2021 dependencies.tar

Known issue?

Originally created by @davetapley on GitHub (Mar 14, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1042 _I will fill this out more later but wanted to get a placeholder in, apologies._ I have ```yml - name: Checkout code uses: actions/checkout@v2 with: lfs: true ``` When pushing to GitHub and running on Actions it gets file: ``` -rw-r--r-- 1 runner docker 185M Mar 14 21:27 dependencies.tar ``` But when running with `act` it doesn't get the file (and so `tar` fails): ``` | -rw-rw-rw- 1 1000 root 134 Aug 24 2021 dependencies.tar ``` Known issue?

kerem added the

kind/bug

stale-exempt

labels

2026-03-01 21:44:54 +03:00

kerem commented

2026-03-01 21:44:54 +03:00

Author

Owner

@davetapley commented on GitHub (Mar 14, 2022):

I tried ⤵️

      - name: Check out LFS objects
        run: GIT_TRACE=1 git lfs fetch -I dependencies.tar

And it hangs here ⤵️

| 21:44:40.945015 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-parse' 'HEAD' '--symbolic-full-name' 'HEAD'
21:44:40.947667 trace git-lfs: tq: running as batched queue, batch size of 100
| 21:44:40.947694 trace git-lfs: fetch dependencies.tar [SHA]
| 21:44:40.947746 trace git-lfs: tq: sending batch of size 1
| 21:44:40.948100 trace git-lfs: api: batch 1 files
| 21:44:40.948228 trace git-lfs: creds: git credential fill ("https", "github.com", "")
| 21:44:40.949540 git.c:439               trace: built-in: git credential fill

So I'm guessing credentials aren't available to LFS, as discussed on https://github.com/git-lfs/git-lfs/issues/4060.
If so them will make repro awkward, as it might need a private repo?

@davetapley commented on GitHub (Mar 14, 2022): I tried ⤵️ ``` - name: Check out LFS objects run: GIT_TRACE=1 git lfs fetch -I dependencies.tar ``` And it hangs here ⤵️ ``` | 21:44:40.945015 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-parse' 'HEAD' '--symbolic-full-name' 'HEAD' 21:44:40.947667 trace git-lfs: tq: running as batched queue, batch size of 100 | 21:44:40.947694 trace git-lfs: fetch dependencies.tar [SHA] | 21:44:40.947746 trace git-lfs: tq: sending batch of size 1 | 21:44:40.948100 trace git-lfs: api: batch 1 files | 21:44:40.948228 trace git-lfs: creds: git credential fill ("https", "github.com", "") | 21:44:40.949540 git.c:439 trace: built-in: git credential fill ``` So I'm guessing credentials aren't available to LFS, as discussed on https://github.com/git-lfs/git-lfs/issues/4060. If so them will make repro awkward, as it might need a private repo?

kerem commented

2026-03-01 21:44:55 +03:00

Author

Owner

@catthehacker commented on GitHub (Mar 14, 2022):

Is that workflow from a private repo?

@catthehacker commented on GitHub (Mar 14, 2022): Is that workflow from a private repo?

kerem commented

2026-03-01 21:44:55 +03:00

Author

Owner

@davetapley commented on GitHub (Mar 14, 2022):

@catthehacker yep

@davetapley commented on GitHub (Mar 14, 2022): @catthehacker yep

kerem commented

2026-03-01 21:44:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 14, 2022):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Apr 14, 2022): Issue is stale and will be closed in 14 days unless there is new activity

kerem referenced this issue

2026-03-01 21:51:32 +03:00

[PR #606] [MERGED] Handle tagless versions #1521

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#606

No description provided.

Rows
Columns