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

Feature: post-save "publishing" notice / `onCommit` hook so editors know changes aren't live yet

Abierto
  • ¿Algo no está bien?
#1,643 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
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience, frontend

Línea de trabajo

Start by tracing the GitHub storage save flow and the existing toastQueue mentioned in the proposal. Compare the smallest built-in notice option with the client-side onCommit hook, and check how UI configuration is defined and tested. Done means editors receive a clear post-save publishing notice or hosts can reliably respond to a successful commit; the issue leaves the preferred option open.

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

Descripción

Problem

In github storage mode, "Save" creates a commit and Keystatic shows Saved. For non-technical editors this reads as "it's live", but the site only updates after CI/CD finishes (for us: a GitHub Actions deploy that debounces saves for 45 s, then builds and publishes, ~2–3 min total). Editors reload the public site right away, see nothing, and assume the save failed; some re-save several times.

Related: #223 (batch deployments, closed → decoupled commits from editing, which doesn't address the feedback gap), #1541 (ready-to-publish flag), #1633 (list view not refreshing after save).

What we do today (workaround)

An Astro middleware injects a small script into /keystatic that wraps window.fetch, detects the createCommitOnBranch mutation succeeding, and shows a toast: "Saved. Publishing… it takes about 2–3 minutes to appear on the site." It works but depends on Keystatic internals.

Proposal (any of these would do)
  1. Config hook — ui: { onCommit?: (info: { branch: string; collection?: string; slug?: string; sha: string }) => void } (client-side). Hosts can show their own notice, start a countdown, or poll their own deploy status.
  2. Built-in notice — ui: { publishNotice?: { message: string } } shown as a toast via the existing toastQueue after a successful commit, with {branch} interpolation. Zero code for most users.
  3. (Later) ui.deployStatus?: () => Promise<'building' | 'live'> polled by Keystatic to show a status pill, letting each site decide what to expose.

Option 2 is the smallest change and covers the most common case: a static message. Happy to open a PR for 1 or 2 if there's interest.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
170
Merge medio
5 h 46 min
PR fusionados (30 d)
3

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 Thinkmill/keystatic

Todos los issues de Thinkmill/keystatic

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.