chore(local): reuse FORGEJO_TOKEN for the auto-patch push #125
Loading…
Reference in a new issue
No description provided.
Delete branch "t3code/forgejo-token-push"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #124 (merged): the auto-patch pipeline required a separate write-scoped
REPO_RW_TOKENto push the branch. Reuse the existingFORGEJO_TOKENinstead.propose-patches.R --open-prnow pushesauto/registry-patch-proposalsover HTTPS withFORGEJO_TOKEN(the same token used for the PR API); the read-onlyoriginclone URL can't push, so it builds an authenticated URL explicitly.REPO_RW_TOKENfrom.crow/auto-apply-patches.yamland the docs.No new secret needed: the pipeline's secrets are now
PGPASS,REPO_RO_TOKEN, andFORGEJO_TOKEN(all existing).FORGEJO_TOKENmust have repository write scope for the push to succeed.105 tests pass; all pre-commit hooks pass.