Block a user
config.yaml: container options are ignored with custom container
Apply resource limitation on container during job
There is an error running under Windows
Thank you for reporting the issue. Could you please provide more details or clarify the image which you upload so that we can better understand and address the problem?
env Variables ara not resolved inside job name
@yekanchi Hi, after reviewing the code, I found that implementing this feature at the moment may be difficult for now. and I found that there are also some similar issues in the Gitea repository. …
Container Options not propagated to job containers
configuration variables
does not work for runs-on
Can you please consider #444 too?
Sure, i will take a look.
45270656df
Set the status of steps to
skipped
if job is skipped (#500)
e14f42c40a
Add ACTIONS_RESULTS_URL to env (#473)
e6630e2e36
Use artifacts v4 jwt if available (#471)
Set the status of steps to
skipped
if job is skipped
sillyguodong
pushed to fix/step_status_skipped at sillyguodong/act_runner
2024-03-01 02:59:18 +00:00
6df2c59b05
fix
sillyguodong
created branch fix/step_status_skipped in sillyguodong/act_runner
2024-03-01 02:59:18 +00:00
Make runs-on support variable expression