Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

SCRIP-SITE-013: publish reviewed Reader through authorized GitHub Pages

Abierto
  • ¿Algo no está bien?
#285 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
devops, release

Línea de trabajo

Start by checking the repository’s Pages publication settings and Actions deployment interlocks using supported authorized tools; the issue says the working identity lacks admin and maintain permissions and that Pages was previously not enabled. Review the existing deployment workflow, then inspect its exact-master build, byte-identity, artifact links, provenance checks, and allowed-path audit. Done means an authorized deployment succeeds and the hosted homepage and work routes are verified; report build, deployment, and live verification separately.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Goal

Make Reader's real source-free results accessible at an actual public URL after approved merge, not merely a successful GitHub Actions build/artifact.

State / capability

Reader 0.2 merged as #276 at 03d122aaf676385ee91e86e5b4cbdf3d212ab752. The repo exposes push=true but admin=false, maintain=false for working identity; prior roadmap reports Pages not enabled. Do not infer current Pages deployment from a build.

Acceptance

  • Check GitHub Pages publication settings and Actions deployment interlocks with only supported authorized tools; do not change admin/access/visibility or secrets without separate authorization.
  • Full exact-master Pages build and double-build byte-identity, artifact content links, license/source/provenance status checks and allowed-path audit.
  • When deploy capability is genuinely granted, deploy through existing reviewed workflow (do not invent a bypass endpoint); re-read deployment result and publicly hosted homepage/work routes.
  • Verify live URL on desktop/mobile/keyboard when permitted. Report BUILT, DEPLOYED and LIVE_VERIFIED separately; blockers affect deployment only, not repo feature development.

2026-10-24 — exact site build and deployment handoff

Owner requested a working, presentable Pages homepage and prominent README URL. Existing site PR #303 contains a real derived-data above-the-fold demo and README link to the intended https://drevendev.github.io/Scriptorium/. Exact branch head de70576db97c13778b41addd8c63d5b2d44ada8a: 23/23 applicable GitHub Actions SUCCESS, 9 site pages, 48 internal links/assets, real comparison/matrix JSON and CSV unchanged. Chromium in-memory artifact previews passed for 1440 and 390px (light/dark), but LIVE_VERIFIED is false.

Actual deployment blocker, no bypass attempted: GitHub repository metadata reports has_pages=false; connected authenticated andy-zen-dev has push=true, admin=false. The allowed connector does not expose Pages administration, and the existing deployment job remains conditional on vars.SCRIPTORIUM_PAGES_DEPLOY_ENABLED == 'true' on master. Neither an Actions build nor a link in README activates Pages.

For an authorized repository administrator (after source-code/data licensing review #284):

  1. In Settings → Pages, select GitHub Actions as the publishing source and enable Pages.
  2. Under Settings → Secrets and variables → Actions → Variables, set SCRIPTORIUM_PAGES_DEPLOY_ENABLED to true. No secret/token is needed for this switch.
  3. After a reviewed PR is merged, run/re-run the existing Scriptorium Pages workflow on master and confirm its Deploy GitHub Pages job actually succeeds.
  4. Load the public homepage, comparison and evidence routes and verify accessibility/links on desktop and mobile. Only then mark DEPLOYED and LIVE_VERIFIED.

No admin, access, visibility, licensing or deployment interlock was changed by this user-facing code PR. A future successful deployment is distinct from the existing successful build.

Lenguaje dominante
Python
Estrellas
4
Forks
0
Merge medio
1 d 8 h
PR fusionados (30 d)
36

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de drevendev/Scriptorium

Todos los issues de drevendev/Scriptorium

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.