Block a user
Revert #90
So my simple idea is to merge upstream changes only when necessary (such as when important features or fixes are added upstream) until we find a better way to develop the runner.
How does it…
Update
nektos/master
branch to 2024.3.12
Bump nektos/act to v0.2.60
Sure, last merge was a bit messy and there was quite a few conflicts. Several tags were skipped between v0.2.51 and v0.2.59. I believe a feature is implemented separately here and in upstream, and…
Bump nektos/act to v0.2.60
6bf9f2c02c99c02a5ed63c499ef2bc93dd5de853 recreates the commits by running git merge v0.2.60
on latest main
. This avoids merging main
to this PR and should make the commit history cleaner.
28c02e857d
Merge tag 'v0.2.60' into bump-nektos-act-v0.2.60
51c16e2691
Improve workflows (#98)
8ba56a0363
Remove emojis in command outputs (#97)
51c16e2691
Improve workflows (#98)
8ba56a0363
Remove emojis in command outputs (#97)
64f0c05713
Merge branch 'main' into bump-nektos-act-v0.2.60
51c16e2691
Improve workflows (#98)
8ba56a0363
Remove emojis in command outputs (#97)
Bump nektos/act to v0.2.60
Does this have a relation to gitea/act#95 or can it merge separately?
No, two PRs are separate. This PR brings nektos/act
v0.2.60
to main branch.
8c83d57212
build(deps): bump golang.org/x/term from 0.17.0 to 0.18.0 (#2244)
119ceb81d9
fix: rootless permission bits (new actions cache) (#2242)
352ad41ad2
fix function name in comment (#2240)
75e4ad93f4
fix: docker buildx cache restore not working (#2236)
934b13a7a1
build(deps): bump github.com/stretchr/testify from 1.8.4 to 1.9.0 (#2235)
0cc67b8817
Support cloning remote actions from insecure Gitea instances (#92)
7e20ddf928
Patched options() to let container options propagate to job containers (#80)
82a3640cf8
Make runs-on support variable expression (#91)
e6fec7324e
Merge pull request 'Bump nektos/act to 0.2.59' (#90) from harryzcy/act:bump-nektos-act into main
73f32886f2
Merge branch 'nektos/master' into bump-nektos