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

/update: the bot is refused on contributors' forks (worked on the owner's fork), and it doesn't log why

Abierto
  • ¿Algo no está bien?
#473 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
65/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, python
Área
devops

Línea de trabajo

Start with the /update workflow code and run 39116506769 to find where the update-branch API response is handled; add failure status and message logging without secrets. Reproduce the request on a contributor fork and compare it with the successful maintainer call. Update CONTRIBUTING.md and docs/AGENT_WORKFLOW.md to describe the confirmed behavior; done when the cause is confirmed and the docs match.

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

Descripción

area: packaging bug priority: P2 size: S

Follow-up to #472 (#464).

During its pre-merge test, /update could update a branch in itsskofficial/Sentient, the repo owner's own fork. On the first real use, on #407 from syedmustafan/Sentient with "Allow edits by maintainers" on, PUT /pulls/{n}/update-branch with the workflow token was refused. The fallback worked as designed: the button hint plus the needs update label. A maintainer then ran the same API call with their own credentials and it succeeded.

So the built-in GITHUB_TOKEN probably can't push to forks owned by other people. It only worked on the admin's own fork. The run log (run 39116506769) also doesn't show the status or message GitHub returned, so this can't be confirmed from the log.

To do:

  1. Log the update-branch response status and message (no secrets) whenever it fails.
  2. Confirm the cause on a contributor fork, and update CONTRIBUTING.md and docs/AGENT_WORKFLOW.md to match. The likely result is that /update merges main on same-repo branches only, and on forks it offers the button and labels the PR for a maintainer. That is fine with our policy, because maintainers handle labelled PRs.
  3. Only if the owner wants it: a GitHub App with contents:write could update fork branches. That needs a setup decision, so don't add new secrets without asking.
Lenguaje dominante
Python
Estrellas
702
Forks
113
Merge medio
5 h 8 min
PR fusionados (30 d)
171

Preparar el entorno

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 existence-master/Sentient

Todos los issues de existence-master/Sentient

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.