mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-10-27 00:31:54 +01:00
ARUNAVO RAYandGitHub
c8618743c8
A fresh install started with scheduling enabled on a plain 24 hour interval counted from first login. The automation card only knows clock schedules, so it showed the 22:00 placeholder as if it were saved while the scheduler ran at whatever time the user first signed in. Toggling the card off and on happened to store the clock schedule and hide the mismatch (#427). The card also showed the browser timezone whenever UTC was stored, so a stored 22:00 UTC read as 22:00 local. New configs start with scheduling off unless SCHEDULE_ENABLED or an interval variable turns it on, with the same rule as the environment loader, and the built-in default is the 22:00 clock schedule the card shows. When a plain interval is stored (SCHEDULE_INTERVAL, GITEA_MIRROR_INTERVAL or an older version) the card says what runs and how it got there, and leaves the frequency and start time unset until the user picks one. The timezone chip shows the stored timezone and turns into a one-click switch to the browser timezone when they differ.