gitea

Files

T

History

Zettat123 31a0c4dfb4 Improve the handling of jobs.<job_id>.if (#31070 )

Fix #25897
Fix #30322

#29464 cannot handle some complex `if` conditions correctly because it
only checks `always()` literally. In fact, it's not easy to evaluate the
`if` condition on the Gitea side because evaluating it requires a series
of contexts. But act_runner is able to evaluate the `if` condition
before running the job (for more information, see
[`gitea/act`](https://gitea.com/gitea/act/src/commit/517d11c67126bd97c88e2faabda0832fff482258/pkg/runner/run_context.go#L739-L753))
. So we can use act_runner to check the `if` condition.

In this PR, how to handle a blocked job depends on its `needs` and `if`:
- If not all jobs in `needs` completed successfully and the job's `if`
is empty, set the job status to `StatusSkipped`
- In other cases, the job status will be set to `StatusWaiting`, and
then act_runner will check the `if` condition and run the job if the
condition is met

2024-05-27 14:15:34 +08:00

auth_test.go

Add interface{} to any replacement to make fmt, exclude *.pb.go (#30461 )

2024-04-13 17:32:15 +00:00

auth.go

Add ac claim for old docker/build-push-action@v3 / current buildx gha cache (#29584 )

2024-03-05 17:34:42 +00:00

cleanup.go

Expire artifacts before deleting them physically (#29241 )

2024-02-18 22:25:14 +08:00

clear_tasks.go

Use db.Find instead of writing methods for every object (#28084 )