From 2f80361083f104c849005448c3c6aedc02a503e3 Mon Sep 17 00:00:00 2001
From: Andrea Arturo Venti Fuentes <117413846+av1155@users.noreply.github.com>
Date: Tue, 11 Aug 2026 12:07:17 -0400
Subject: [PATCH] ci: re-register star history schedule

The workflow file landed on main during the 6 August Actions
incident, when workflow-triggering events were dropped and could
not be replayed, so its cron was never registered. Changing the
minute forces a resync on the next default-branch push.

Add the watch trigger so a star refreshes the chart directly
rather than leaving it dependent on the cron registration alone,
and cancel superseded runs since each one rebuilds from the full
stargazer list.

Closes #721
---
 .github/workflows/star-history.yml | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/star-history.yml b/.github/workflows/star-history.yml
index 8300efa6..8261361c 100644
--- a/.github/workflows/star-history.yml
+++ b/.github/workflows/star-history.yml
@@ -2,9 +2,14 @@ name: Star History
 
 on:
   schedule:
-    # Daily at 07:23 UTC. Off-the-hour on purpose: GitHub queues scheduled
+    # Daily at 07:41 UTC. Off-the-hour on purpose: GitHub queues scheduled
     # workflows hardest at the top of the hour, so an odd minute starts sooner.
-    - cron: "23 7 * * *"
+    - cron: "41 7 * * *"
+  # Stargazers are this chart's only input, so refresh on the star itself rather
+  # than waiting out the day. The cron stays as the backstop: `started` is the
+  # only activity type `watch` has, so unstarring never reaches here.
+  watch:
+    types: [started]
   workflow_dispatch:
 
 permissions:
@@ -12,7 +17,9 @@ permissions:
 
 concurrency:
   group: ${{ github.workflow }}
-  cancel-in-progress: false
+  # Every run rebuilds from the full stargazer list, so a newer run supersedes an
+  # older one outright. Without this a rush of stars queues one serial run each.
+  cancel-in-progress: true
 
 jobs:
   refresh: