Zettat123 ac1ba34518 Fix incorrect job result status (#40) ...

Fix [#24039(GitHub)](https://github.com/go-gitea/gitea/issues/24039)

At present, if a job fails in the `Set up job`, the result status of the job will still be `success`. The reason is that the `pre` steps don't call `SetJobError`, so the `jobError` will be nil when `post` steps setting the job result. See https://gitea.com/gitea/act/src/commit/5c4a96bcb797c7d013b878f1a3ceb74f9a834c64/pkg/runner/job_executor.go#L99

Reviewed-on: https://gitea.com/gitea/act/pulls/40
Reviewed-by: Jason Song <i@wolfogre.com>
Co-authored-by: Zettat123 <zettat123@gmail.com>
Co-committed-by: Zettat123 <zettat123@gmail.com>

2023-04-14 15:42:03 +08:00

..

artifacts

fix: tolerate workflow that needs a missing job (#1595) (#1619)

2023-02-16 16:41:59 +00:00

common

Merge tag 'nektos/v0.2.43'

2023-03-16 11:45:29 +08:00

container

Merge tag 'nektos/v0.2.43'

2023-03-16 11:45:29 +08:00

exprparser

Support gitea context (#27)

2023-03-23 12:14:28 +08:00

jobparser

Avoid using log.Fatal in pkg/* (#39)

2023-04-07 16:31:03 +08:00

lookpath

feat: Host environment (#1293)

2022-11-16 21:29:45 +00:00

model

Avoid using log.Fatal in pkg/* (#39)

2023-04-07 16:31:03 +08:00

runner

Fix incorrect job result status (#40)

2023-04-14 15:42:03 +08:00

workflowpattern

feat: workflowpattern package (#1618)

2023-02-23 18:21:08 +00:00