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

Route v13 API-docs CI and publication to website branch v13

Abierto
  • ¿Algo no está bien?
#8,753 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions
Área
ci-cd

Línea de trabajo

Start with the api-docs job in .github/workflows/ci.yml and the publish job in .github/workflows/publish.yml, and find where each checks out the website's default branch. Add a step that derives the compiler major from the version, including prereleases, and maps 12 to master and 13 to v13. Then confirm that the artifact lands in data/api and that publishing commits to the chosen branch. Done means both workflows select the branch correctly for stable and alpha versions, and the v12 path is unchanged. Website #1433 must land first.

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

Descripción

Compiler master generates v13 API snapshots, but both the API-docs CI check and release publication check out the website's default branch. Website master selects v12 data, so building it with a new v13 artifact does not validate v13 API pages, and publishing there does not update the website's v13 branch.

Target branch: compiler master (v13). This changes workflow routing, not compiler language behavior.

  • In .github/workflows/ci.yml, make the api-docs job check out the matching website branch before downloading and building the generated artifact.
  • In .github/workflows/publish.yml, use the same branch mapping for the website checkout, build, and API-data commit/push.
  • Map compiler major 12 to website master, and compiler major 13 to website v13. Derive the major from the compiler/release version, including prereleases.
  • Download artifacts into repository-root data/api, and require a successful build of the matching website before publishing its API-data changes.

Acceptance: v13 CI builds website branch v13 with the incoming v13 snapshot; v13 release publication commits that snapshot to v13 and triggers the appropriate website deployment. Verify branch selection for stable and alpha versions, and preserve the v12 maintenance publication path to website master.

Prerequisite: website #1433 must land first so the v13 website consumes and validates the published data. Confirm the v13 website deployment trigger as part of the coordinated rollout.

Related: website #1391 and website PR #1432.

Lenguaje dominante
OCaml
Estrellas
7.5k
Forks
484
Merge medio
19 h 46 min
PR fusionados (30 d)
81

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 rescript-lang/rescript

Todos los issues de rescript-lang/rescript

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.