Skip to content

fix(fork): revive the nightly schedule GitHub dropped #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
not-compromised merged 1 commit into from
Oct 12, 2026
Merged

fix(fork): revive the nightly schedule GitHub dropped #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/fork-nightly.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ on:
schedule:
# Finishes before the owner's 08:30 UTC digest scan, which reports a fork
# still behind upstream; servers install the release within 30 minutes.
- cron: "30 7 * * *"
# GitHub drops a public repo's schedules after 60 days without activity
# and revives them only when a person commits a change to this line.
- cron: "35 7 * * *"
workflow_dispatch:
inputs:
target_tag:
Expand Down
4 changes: 2 additions & 2 deletions FORK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ nightly.

## Nightly pipeline

`.github/workflows/fork-nightly.yml` runs daily at 07:30 UTC and on demand.
`.github/workflows/fork-nightly.yml` runs daily at 07:35 UTC and on demand.

1. It picks the newest upstream nightly release tag.
2. It refuses to ship by itself if `ORCHESTRATION_PROTOCOL_VERSION` changed,
Expand Down Expand Up @@ -124,7 +124,7 @@ otherwise.

- **Commits:** `chore(fork): nightly rolling rebase and release pipeline`
- **Must still be true:**
- Daily at 07:30 UTC and on demand, the newest upstream nightly gets
- Daily at 07:35 UTC and on demand, the newest upstream nightly gets
`custom` replayed onto it, checked and built; it ships only when every
step is green.
- A changed `ORCHESTRATION_PROTOCOL_VERSION` never ships without
Expand Down
Loading