chore(local): reuse FORGEJO_TOKEN for the auto-patch push #125

Merged
pat-s merged 1 commit from t3code/forgejo-token-push into main 2026-07-15 14:50:19 +00:00
Owner

Follow-up to #124 (merged): the auto-patch pipeline required a separate write-scoped REPO_RW_TOKEN to push the branch. Reuse the existing FORGEJO_TOKEN instead.

  • propose-patches.R --open-pr now pushes auto/registry-patch-proposals over HTTPS with FORGEJO_TOKEN (the same token used for the PR API); the read-only origin clone URL can't push, so it builds an authenticated URL explicitly.
  • Drop REPO_RW_TOKEN from .crow/auto-apply-patches.yaml and the docs.

No new secret needed: the pipeline's secrets are now PGPASS, REPO_RO_TOKEN, and FORGEJO_TOKEN (all existing). FORGEJO_TOKEN must have repository write scope for the push to succeed.

105 tests pass; all pre-commit hooks pass.

Follow-up to #124 (merged): the auto-patch pipeline required a separate write-scoped `REPO_RW_TOKEN` to push the branch. Reuse the existing `FORGEJO_TOKEN` instead. - `propose-patches.R --open-pr` now pushes `auto/registry-patch-proposals` over HTTPS with `FORGEJO_TOKEN` (the same token used for the PR API); the read-only `origin` clone URL can't push, so it builds an authenticated URL explicitly. - Drop `REPO_RW_TOKEN` from `.crow/auto-apply-patches.yaml` and the docs. No new secret needed: the pipeline's secrets are now `PGPASS`, `REPO_RO_TOKEN`, and `FORGEJO_TOKEN` (all existing). `FORGEJO_TOKEN` must have repository write scope for the push to succeed. 105 tests pass; all pre-commit hooks pass.
Push the auto/registry-patch-proposals branch over HTTPS with FORGEJO_TOKEN (the
same token already used for the PR API), so no separate write-scoped REPO_RW_TOKEN
secret is needed. Drop it from propose-patches.R, the pipeline, and the docs.
pat-s merged commit 1bca6004fd into main 2026-07-15 14:50:19 +00:00
pat-s deleted branch t3code/forgejo-token-push 2026-07-15 14:50:19 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
devxy/build-cran-binaries!125
No description provided.