Publish the page to GitHub Pages after every successful scan - #119
Merged
Merged
Conversation
.github/workflows/pages.yml runs when daily-scan completes successfully (workflow_run), on pushes to main touching the page's files, and on demand: checkout with history, tools/evaluate_signals.py --json for the track record, tools/build_site.py into _site/, then configure-pages, upload-pages-artifact and deploy-pages (SHA-pinned). A dispatch from a branch builds without deploying; a failed scan leaves the previous build. Pages is enabled with the GitHub Actions source. README, wiki 01 and 04, daily-scan comment, changelog. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…main only Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.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
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
PR 3 of the website plan: publish the page at https://yanivil.github.io/SignalSync/ after every successful scan.
Workflow
.github/workflows/pages.ymlworkflow_runwhendaily-scancompletes successfully (a push made with the workflow token, like the scan's commit ofoutput/, never triggers other workflows, so the scan's completion is the trigger); pushes touching the page's files (site/,tools/build_site.py,tools/evaluate_signals.py, the workflow); manual dispatch. A failed scan leaves the previous build in place.build: checkout with history,tools/evaluate_signals.py --horizon 60 --json(the runner has the open internet the prices need),tools/build_site.pyinto_site/,configure-pages,upload-pages-artifact. Nothing is committed back.deploy:deploy-pagesinto thegithub-pagesenvironment, onmainonly; a branch push builds without deploying, which is the smoke test. Permissionscontents: read,pages: write,id-token: write; concurrency per ref; all actions SHA-pinned (configure-pages v6.0.0, upload-pages-artifact v5.0.0, deploy-pages v5.0.1).mainruns).Smoke test on this branch: run 34328987082 evaluated the six live signals, built the page (1 setup, 5 watchlist rows, 6 track-record rows) and uploaded the artifact; the deploy job was skipped as designed.
Docs: README (the page's URL and the layout entry), wiki 01 (scheduling diagram and the publishing bullet), wiki 04 (workflows table), a note in
daily-scan.yml, changelog.After the merge: the push to
maintouching the workflow triggers the first build and deploy; from then on every successful nightly scan republishes the page. The 08:45 e-mail task is untouched; retiring it or shrinking it to a one-line link is a separate decision.Test plan
maintestsworkflow on this PRmainafter the merge, then open https://yanivil.github.io/SignalSync/🤖 Generated with Claude Code