Skip to content

Publish the page to GitHub Pages after every successful scan - #119

Merged
yanivil merged 2 commits into
mainfrom
feat/pages
Sep 9, 2026
Merged

yanivil merged 2 commits into
mainfrom
feat/pages

Conversation

@yanivil

@yanivil yanivil commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Summary

PR 3 of the website plan: publish the page at https://yanivil.github.io/SignalSync/ after every successful scan.

Workflow .github/workflows/pages.yml

  • Triggers: workflow_run when daily-scan completes successfully (a push made with the workflow token, like the scan's commit of output/, 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.py into _site/, configure-pages, upload-pages-artifact. Nothing is committed back.
  • deploy: deploy-pages into the github-pages environment, on main only; a branch push builds without deploying, which is the smoke test. Permissions contents: 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).
  • Pages is enabled on the repository with the GitHub Actions source (done through the API; the URL above is live once the first deploy from main runs).

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 main touching 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

  • branch smoke build (34328987082): evaluate, build, artifact upload; deploy skipped off main
  • tests workflow on this PR
  • first deploy from main after the merge, then open https://yanivil.github.io/SignalSync/

🤖 Generated with Claude Code

yanivil and others added 2 commits September 9, 2026 11:24
.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>
@yanivil
yanivil merged commit a428849 into main Sep 9, 2026
6 of 7 checks passed
@yanivil
yanivil deleted the feat/pages branch September 9, 2026 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant