-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
topic/gitea-actionsrelated to the actions of Gitearelated to the actions of Giteatype/bugtype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.
Description
Feature Description
It is my understanding that Github Actions schedule objects are all interpreted as UTC. After configuring some cron workflows and setting them to run at 9AM, I have noticed that they run at 9AM local time and not 9AM UTC. I am unsure if this was an intended effect or could be viewed as a bug.
I see the following as paths forward:
- Document that workflow schedules are configured to local time
- Change workflow schedules to instead be based on UTC
- Add a configuration value to allow cron to be interpreted as either local or UTC, default to use local to retain current behaviors and add documentation to clarify
For posterity here is my observed behavior:
Given a workflow defined to run as
on:
schedule:
- cron: "0 9 * * *"
I see job ran ~25 minutes ago at roughly that amount of time past 9AM local
Screenshots
Metadata
Metadata
Assignees
Labels
topic/gitea-actionsrelated to the actions of Gitearelated to the actions of Giteatype/bugtype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.