Skip to content

chore(daily-status): move schedule to 08:00 SGT (00:00 UTC)#127

Merged
arnaudlh merged 1 commit into
mainfrom
chore/daily-status-schedule-sgt
May 28, 2026
Merged

chore(daily-status): move schedule to 08:00 SGT (00:00 UTC)#127
arnaudlh merged 1 commit into
mainfrom
chore/daily-status-schedule-sgt

Conversation

@arnaudlh

Copy link
Copy Markdown
Member

Switches the daily-repo-status workflow from the gh-aw schedule: daily fuzzy default (which had been compiling to 25 10 * * * UTC ≈ 18:25 SGT) to a fixed 0 0 * * * UTC, i.e. 08:00 SGT every day.

Why

  • The fuzzy daily run had been missing days recently (last successful schedule: May 25; May 26 and May 27 skipped — typical GitHub-Actions scheduled-workflow drop behaviour).
  • Pinning to an explicit UTC hour makes monitoring easier and aligns delivery with the start of the SGT workday.

Files

  • .github/workflows/daily-repo-status.md — source: switched schedule: daily → explicit cron.
  • .github/workflows/daily-repo-status.lock.yml — mirrors the cron change (single-line patch; full gh aw compile was skipped to avoid sweeping in unrelated tool-version drift).

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the daily repo status agentic workflow schedule from a fuzzy daily trigger to an explicit UTC cron intended to run at 08:00 SGT.

Changes:

  • Replaces schedule: daily in the workflow source with an explicit cron schedule.
  • Mirrors the cron change in the compiled lock workflow.
Show a summary per file
File Description
.github/workflows/daily-repo-status.md Updates the source workflow schedule to 0 0 * * * with an SGT/UTC comment.
.github/workflows/daily-repo-status.lock.yml Updates the compiled workflow cron to match the intended schedule.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 3

"on":
schedule:
- cron: "25 10 * * *"
- cron: "0 0 * * *"
Comment on lines +9 to +11
# 08:00 SGT (UTC+8) every day = 00:00 UTC
schedule:
- cron: "0 0 * * *"
"on":
schedule:
- cron: "25 10 * * *"
- cron: "0 0 * * *"
@arnaudlh arnaudlh requested a review from dawright22 May 27, 2026 02:48
@sendtoshailesh

Copy link
Copy Markdown
Contributor

Review summary

Targeted, low-risk schedule change. Reviewed the diff against daily-repo-status.md and daily-repo-status.lock.yml:

Correctness

  • Time math checks out: cron: "0 0 * * *" UTC + 8h = 08:00 SGT
  • Source .md and compiled .lock.yml cron values are in sync (0 0 * * * in both) ✅
  • All 5 checks pass (Analyze, Markdown Lint, Structural Validation, actionlint, CLA) ✅
  • Skipping a full gh aw compile to avoid sweeping in unrelated drift is a reasonable trade-off given the single-line nature of the change

Minor nits (non-blocking)

  1. Stale comment in daily-repo-status.lock.yml:58:

    - cron: "0 0 * * *"
      # Friendly format: daily (scattered)

    The "(scattered)" hint described the old schedule: daily fuzzy default; with an explicit cron it's now misleading. Either drop the comment or replace it with "08:00 SGT (00:00 UTC)" to match the source .md.

  2. Heads-up on top-of-hour scheduling: 0 0 * * * lands on the highest-traffic GH Actions cron slot, which is the slot most prone to delays/drops. If reliability is the actual goal (the PR body cites recent missed runs), an off-peak minute like 7 0 * * * would still give an ~08:07 SGT start but with a notably better hit rate. Worth keeping in mind if days continue to be skipped after this lands.

Otherwise LGTM — clean fix for the missed-runs symptom and easier to monitor than the fuzzy default. 👍

@arnaudlh arnaudlh merged commit 022208f into main May 28, 2026
6 checks passed
@arnaudlh arnaudlh deleted the chore/daily-status-schedule-sgt branch May 28, 2026 00:12
arnaudlh added a commit to arnaudlh/git-ape that referenced this pull request May 29, 2026
…t source

PR Azure#136 regenerated the lock file before PR Azure#127 (08:00 SGT schedule)
landed on main. The merged lockfile carries the frontmatter_hash for the
pre-SGT source ('schedule: daily'), so every run fails the integrity
check with:

  ERR_CONFIG: Lock file '.github/workflows/daily-repo-status.lock.yml'
  is outdated! The workflow file '.github/workflows/daily-repo-status.md'
  frontmatter has changed.

Recompiled with gh aw v0.76.1 against the current source so the
frontmatter_hash matches what the runtime computes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants