type: service
status: active
timestamp: 2026-06-20
tags: [cron, github, actions, primary]

GitHub Actions schedule (cron)

Build- and publish-shaped scheduled jobs on GitHub Actions — free for public repos

GitHub Actions schedule (cron)

Role

Scheduled jobs that need a build environment — Node + pnpm, secrets, repo checkout, the ability to commit results back to a repo or publish to npm / a registry / a deploy target.

This is the sister substrate to Cloudflare Cron Triggers. The two together implement the cron split.

Free tier

Card / subscription required?

NO. Free for personal accounts on public repos with no payment method on file.

What we run on it

JobRepoCadenceWhy GH Actions
oriz-omnipost RSS cross-post runoriz-omnipostevery 30 minCommits state.json back to repo; needs pnpm + adapters’ fetch tokens
Master deploy matrix on pointer-bumporizon push (not strictly cron, sibling workflow)Needs wrangler + each site’s secrets
Dependabot security update sweepevery repodailyGitHub-native
npm publish of @chirag127/oriz-kit etc. on tagorizon tag (sibling workflow)Needs pnpm + npm token
Per-site GitHub Pages mirror buildeach oriz-*-sitenightly + on pushNeeds pnpm build
Lifestream JSONL ingest (push window)oriz-me-datahourlyNeeds gh CLI + repo write

Alternatives

Swap cost

Low — workflow YAML is mostly portable. cron: triggers move to schedule: on most runners. Repo write commits would need a different bot identity off-platform.

Why this is our pick

For build / publish / “commit results back” jobs, GH Actions has the toolchain, the secrets, and the repo write access already wired together. Free at our scale on public repos. Failures show up in a dashboard humans already watch.

Cross-refs


Edit on GitHub · Back to index