You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #40. OpenCite is currently served from the legacy gh-pages branch (Settings > Pages reports build_type: legacy). There is no automatic Pages deploy running from main yet. PR #72 introduces an official GitHub Pages artifact/deploy workflow, but local tests and PR CI alone do not verify that the live site updates.
Change Settings > Pages > Build and deployment > Source to GitHub Actions. This is a one-time repository setting; no deployment token should be needed.
If the merge-triggered workflow ran before the source setting changed, run Deploy GitHub Pages manually once from main.
Confirm a subsequent push to main triggers a successful deploy and updates the live site without manual steps.
Acceptance criteria
Pages uses GitHub Actions as its deployment source.
The Deploy GitHub Pages workflow completes successfully from main after tests, metadata validation, and build.
The live site serves the built output, including the expected current commit's assets.
A later push to main updates the live site automatically; no manual deployment is needed for future commits.
Related: #40 (original completed deployment task); implementation PR: #72. Keep this issue open until the live behavior is verified, not merely until the PR merges.
Context
Follow-up to #40. OpenCite is currently served from the legacy
gh-pagesbranch (Settings > Pagesreportsbuild_type: legacy). There is no automatic Pages deploy running frommainyet. PR #72 introduces an official GitHub Pages artifact/deploy workflow, but local tests and PR CI alone do not verify that the live site updates.Work
gh-pagesbranch as a fallback until deployment is verified.main./OpenCite/.maintriggers a successful deploy and updates the live site without manual steps.Acceptance criteria
Deploy GitHub Pagesworkflow completes successfully frommainafter tests, metadata validation, and build.mainupdates the live site automatically; no manual deployment is needed for future commits.Related: #40 (original completed deployment task); implementation PR: #72. Keep this issue open until the live behavior is verified, not merely until the PR merges.