Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Please add timezones to cron schedules

See original GitHub issue

Describe the enhancement Please add timezones to cron schedules.

Code Snippet

name: Timed action
on:
  schedule:
    - cron: '01 20 * * 1-5'
    - timezone: 'Australia/Melbourne'

Additional information Especially when the schedule is only supposed to run on certain days of the week this gets very confusing with UTC. Daylight savings does not help much either here.

Issue Analytics

State:
Created 2 years ago
Reactions:124
Comments:6 (2 by maintainers)

Top GitHub Comments

12reactions

cj81499commented, Mar 24, 2022

It didn’t look like anyone started a discussion, like @ethomson suggested, so I started one. https://github.com/github/feedback/discussions/13454

7reactions

sammcjcommented, Oct 21, 2021

FYI We logged an enterprise support ticket for this:

(GitHub Support) Oct 21, 2021, 9:35 AM UTC

While specifying the cron schedule in a timezone other than UTC is not yet supported, we have an internal feature request tracking feedback from other customers.

I have added this ticket to the discussion.

This is not on our public roadmap so I do not have any links I can share with you at the moment, sorry. I am unable to provide a timeline of when this will be supported but you can keep an eye on the ChangeLog page of our Blog where we announce features when they become available.