ci: rebuild on repository_dispatch from product doc repos#4
Closed
andybons wants to merge 1 commit into
Closed
Conversation
Product repos can now fire a docs-updated event to trigger an immediate rebuild instead of waiting for the daily cron.
Contributor
Author
|
Closing alongside gatekeeper#52 — the daily rebuild cron covers doc-staleness without needing a cross-repo dispatch token. See gatekeeper#52 for the reasoning. |
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
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.
What
Adds a
repository_dispatchtrigger (types: [docs-updated]) to the deploy workflow, alongside the existing push / workflow_dispatch / daily schedule triggers.Product repos (starting with gatekeeper — see its paired
notify-site.ymlPR) fire this event when their docs change on main, so the site redeploys within a minute of a docs merge instead of waiting up to 24h for the scheduled rebuild. The daily cron stays as the fallback for when the dispatch token is absent or the event is missed.No other workflow changes.