Deploy the dashboard after the weekly reporting run - #30
Open
marvinm2 wants to merge 1 commit into
Open
Conversation
The reporting workflow commits docs/index.html using GITHUB_TOKEN. A push made with that token does not trigger another workflow, so the paths filter on the push trigger here never matched the weekly commit, and the site was last deployed on 2026-07-01 while the reports kept updating. Adding a workflow_run trigger keyed to the reporting workflow deploys after it finishes, and the job is skipped when that run did not succeed.
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.
Closes #25.
The reporting workflow commits
docs/index.htmlusingGITHUB_TOKEN, and a push made with that token does not trigger another workflow, so thepathsfilter on the push trigger here never matched the weekly commit.Adding a
workflow_runtrigger keyed to the reporting workflow deploys after it finishes. The job is skipped when that run did not succeed, so a failed collection does not publish over good numbers.The push and
workflow_dispatchtriggers are left as they are.One caveat: a
workflow_runtrigger only takes effect once it is on the default branch, so this cannot be demonstrated from a fork. I have checked the YAML parses and the condition is right, but the first real proof will be the Monday run after it merges.