Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#473 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, python
Ambito
devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Python
Stelle
702
Fork
113
Merge medio
5h 6m
PR unite (30g)
172

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di existence-master/Sentient

Tutte le issue di existence-master/Sentient

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.