ci: daily 2am rebuild + preserve fork-local workflows#5
Merged
DavidBellamy merged 1 commit intomainfrom Apr 18, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two changes to
.github/workflows/maintain-deploy.yml, coordinated across all 5 LLM360 forks (miles, sglang, smg, harbor, Megatron-LM):Cron cadence: changed from
*/15 * * * *(every 15 minutes) to0 2 * * *(daily at 2 AM UTC). The 15-minute rebuild was wasteful given that upstream moves and our fork-only PR set both churn slowly; daily is sufficient.Preserve fork-local
.github/workflows: added a new step right before the fingerprint-and-push step. It overlays.github/workflows/from the fork's default branch onto the rebuilt deploy tree.Why: GitHub Actions only reads workflow files on the branch where the trigger fires. Fork-local CI like
release-binary.yml(which hason: push: branches: [deploy]) lives only on main and never made it onto the deploy branch, so its triggers never fired. With this step, any workflow present on main is carried forward to deploy on every rebuild.This PR is part of a coordinated rollout to all 5 LLM360 forks (miles, sglang, smg, harbor, Megatron-LM).