Restore and verify automatic GitHub Pages deployment from main
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions, javascript
Research direction
Start by reviewing PR #72 and the Deploy GitHub Pages workflow, then check Settings > Pages to confirm the deployment source and run status. Verify the site at https://imageomics.github.io/OpenCite/ serves the built app and assets under /OpenCite/, and confirm that a later push to main triggers a successful update without manual deployment.
Written by the indexing model from the issue text.
Description
Context
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.
Work
- Merge #72 after review. Keep the existing
gh-pagesbranch as a fallback until deployment is verified. - 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. - Verify that the deployment workflow succeeds and https://imageomics.github.io/OpenCite/ loads the newly built app and assets under
/OpenCite/. - Confirm a subsequent push to
maintriggers a successful deploy and updates the live site without manual steps.
Acceptance criteria
- Pages uses GitHub Actions as its deployment source.
- The
Deploy GitHub Pagesworkflow completes successfully frommainafter tests, metadata validation, and build. - The live site serves the built output, including the expected current commit's assets.
- A later push to
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.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 5
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Imageomics/OpenCite
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Imageomics/OpenCite#66 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Imageomics/OpenCite#68 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Imageomics/OpenCite#69 ·
Maintainers usually reply within 1 day
-
Fix contributor fallback limit when automated accounts are presentPossibly taken @beanbean9339 claimed this 18 days ago. Open
Imageomics/OpenCite#56 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Imageomics/OpenCite#55 ·
Maintainers usually reply within 1 day
All issues in Imageomics/OpenCite
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
solana-foundation/solana-com#2202 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
yegor256/copyrights-action#216 ·
-
[BUG] onScroll never refreshes the window container's height after a vertical-only viewport resizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
juliangarnier/anime#1192 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PedestrianDynamics/pyFDS-Evac#226 ·
Maintainers usually reply within 1 day