diff options
| author | Jason Song <i@wolfogre.com> | 2024-08-01 18:02:46 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-01 10:02:46 +0000 |
| commit | 21a73ae642b15982a911837775c9583deb47220c (patch) | |
| tree | c3a3783df7addb116acb2dca64be3535dad798a7 /services/pull | |
| parent | 333c9ed8cab961b6dd58b04edc47a57dc4d6dbab (diff) | |
| download | gitea-21a73ae642b15982a911837775c9583deb47220c.tar.gz gitea-21a73ae642b15982a911837775c9583deb47220c.zip | |
Use UTC as default timezone when schedule Actions cron tasks (#31742)
Fix #31657.
According to the
[doc](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onschedule)
of GitHub Actions, The timezone for cron should be UTC, not the local
timezone. And Gitea Actions doesn't have any reasons to change this, so
I think it's a bug.
However, Gitea Actions has extended the syntax, as it supports
descriptors like `@weekly` and `@every 5m`, and supports specifying the
timezone like `TZ=UTC 0 10 * * *`. So we can make it use UTC only when
the timezone is not specified, to be compatible with GitHub Actions, and
also respect the user's specified.
It does break the feature because the times to run tasks would be
changed, and it may confuse users. So I don't think we should backport
this.
## ⚠️ BREAKING ⚠️
If the server's local time zone is not UTC, a scheduled task would run
at a different time after upgrading Gitea to this version.
Diffstat (limited to 'services/pull')
0 files changed, 0 insertions, 0 deletions