Support hashFiles
#40
Labels
No Label
kind
bug
kind
build
kind/compatible
kind
dependencies
kind
docs
kind
enhancement
kind
feature
kind
help wanted
kind
proposal
kind
refactor
related
act
related
environment
related
exec
related
gitea
related
workflow
reviewed
confirmed
reviewed
duplicate
reviewed
invalid
reviewed
needs feedback
reviewed
wontfix
reviewed
workaround
No Milestone
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/act_runner#40
Loading…
Reference in New Issue
Block a user
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?
About
hashFiles
:See https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows
act_runner will panic when using
hashFiles
, it could be fixed by https://github.com/nektos/act/pull/1667 , but it cannot make act_runner support it.Because there's no code files in local disk for act_runner to read, the files could be in containers.
hashfiles in act is broken by design, act should probably run it within the "container" by using node and the hashfiles js script of actions/runner.
The following seems to require adding hashfiles as an externally defined function, in the current place is no container instance or dependency
Just an indea, but hashfiles doesn't gain much attention for me
https://gitea.com/actions/go-hashfiles
I created an action that computes SHA256 checksum for specified files. I think this action can provide similar function until act_runner fully supports
hashFiles
.https://gitea.com/seepine/hash-files or https://github.com/seepine/hash-files
I created an action that computes SHA256 base on node.
It doesn't need to
setup-go
when runs-onubuntu-latest
BTW I currently use this patch in my act fork
(
aec5ff7a02
,dd3cfce42d
)Better user experience than rewriting workflows.
I'm not shure how clean these can be applied to nektos/act and gitea/act
I plan to create a pr to nektos/act at some point of time
Of course, it is best for act to directly support hashFiles, looking forward to your PR
https://github.com/nektos/act/pull/1940
seepine/hash-files
is much faster thanactions/go-hashfiles
(0 second vs 16 seconds)it seems that actions written in Go are slow due to the building process.