feat: notify FuSaOps on release for instant image rebuild - #48
Merged
Conversation
FuSaOps' tools-monitor.yml has always supported an xfusa-released repository_dispatch for instant rebuilds, but no x-FuSa repo except rust-FuSa actually sent it -- every tool release has only ever reached FuSaOps via the weekly cron. Add the same notify step rust-FuSa uses. Signed-off-by: Matt Jones <47545907+SoundMatt@users.noreply.github.com>
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
tools-monitor.ymlhas always supported anxfusa-releasedrepository_dispatchfor instant rebuilds, but no x-FuSa repo except rust-FuSa actually sends it — every tool release has only ever reached FuSaOps via its weekly cron.Notify FuSaOpsstep rust-FuSa'srelease.ymlalready uses, at the end of the Docker publish job.FUSAOPS_DISPATCH_TOKENsecret (a PAT with write access toSoundMatt/FuSaOps) to actually fire;continue-on-error: truemeans it's a safe no-op until that secret exists, falling back to the existing weekly cron.Test plan
continue-on-errorsafety)