BackendBench
Coffee

Home โ€บ GitHub Actions โ€บ Every Saturday and Sunday at 10:00 AM

GitHub Actions cron

GitHub Actions cron expression: every Saturday and Sunday at 10:00 AM

To run a GitHub Actions job every Saturday and Sunday at 10:00 AM, use:

0 10 * * 0,6

At 10:00 UTC, on Sun and Sat.

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

Weekend-only work: batch jobs that should not compete with weekday traffic.

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

#Date and time (UTC)
1Sat, 02 Jan 2027, 10:00:00
2Sun, 03 Jan 2027, 10:00:00
3Sat, 09 Jan 2027, 10:00:00
4Sun, 10 Jan 2027, 10:00:00
5Sat, 16 Jan 2027, 10:00:00
6Sun, 17 Jan 2027, 10:00:00

Every Saturday and Sunday at 10:00 AM in every dialect

SystemExpression
GitHub Actions (this page)0 10 * * 0,6
Quartz0 0 10 ? * 1,7
Spring0 0 10 * * 0,6
Crontab0 10 * * 0,6
Kubernetes0 10 * * 0,6
AWS EventBridge0 10 ? * 1,7 *
JenkinsH 10 * * 0,6
node-cron0 10 * * 0,6
Apache Airflow0 10 * * 0,6
Azure Functions0 0 10 * * 0,6
Google Cloud Scheduler0 10 * * 0,6

Need to translate a different expression? Use the cron converter.

Ready-to-use GitHub Actions config

Drop this into your project. The expression is the one above.

Workflow trigger
on:
  schedule:
    - cron: "0 10 * * 0,6"

The GitHub Actions fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).

Things to watch out for in GitHub Actions

The common mistake with this schedule

Sunday is 0 (or 7) in Unix, and 1 in Quartz and EventBridge. Saturday is 6 in Unix but 7 in Quartz.

Frequently asked questions

How do I run a GitHub Actions job every Saturday and Sunday at 10:00 AM?

Use 0 10 * * 0,6. At 10:00 UTC, on Sun and Sat.

What is the every Saturday and Sunday at 10:00 AM cron expression in other systems?

Quartz: 0 0 10 ? * 1,7; Spring: 0 0 10 * * 0,6; Crontab: 0 10 * * 0,6. The table on this page lists every dialect.

Which time zone does GitHub Actions use for this schedule?

GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.

Similar GitHub Actions schedules

More tools you might need