mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #1242] unable to get git repo #684
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#684
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 @mrcnski on GitHub (Jul 5, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1242
Bug report info
Command used with act
Describe issue
Tons and tons of error message spam in the output.
Link to GitHub repository
https://github.com/SkynetLabs/skynet-js
Workflow content
Relevant log output
etc.
@ZauberNerd commented on GitHub (Jul 5, 2022):
That's probably because you're executing act in a folder that doesn't contain a
.gitfolder: https://github.com/nektos/act/blob/master/pkg/common/git/git.go#L226-L249Also, these messages are warnings, not errors.
@mrcnski commented on GitHub (Jul 5, 2022):
There is a
.gitfile (not folder), my repo happens to be a worktree. That seems to be what's causing it, based on the linked code.This might be easily fixed if you use the
gitdirspecified in the worktree file, though you'd have to test it. I can even give it a shot if you reopen the issue.@ZauberNerd commented on GitHub (Jul 5, 2022):
There was an attempt a few months ago to implement worktree support in act: https://github.com/nektos/act/pull/829 but unfortunately it was abandoned.
If you want to try to implement it, please go ahead :)
@mrcnski commented on GitHub (Jul 5, 2022):
I guess it's not as simple as just changing that one function:
I don't have the inclination to dive into
actinternals; I barely use it, I just wanted to report a single issue.It would be nice if at least the
giterror only displayed once instead of 1000s of times, but I likewise don't care to learn howactimplements its error handling in order to fix that.@KnisterPeter commented on GitHub (Jul 5, 2022):
If you don't care, you don't deserve the fix 😉
Just joking.
@mrcnski commented on GitHub (Jul 5, 2022):
The maintainers could fix this really quickly as they already are familiar with the codebase.