From 3f30f889c3a524ec8dd9e67cf3f801bf4db5e229 Mon Sep 17 00:00:00 2001 From: lilleman Date: Sun, 2 Aug 2026 15:48:04 +0200 Subject: [PATCH] README: note GITHUB_ secret-name prefix is rejected too --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d78373a..22f57f9 100644 --- a/README.md +++ b/README.md @@ -1249,8 +1249,8 @@ Renovate merges it once `CI / full-gate (push)` is green (rebasing stale branche fast-forward-only merge still holds) — routine bumps land untouched; only a red gate needs a human. One-time setup: reuse the shared `renovate@larvit.se` bot — give it write access to this repo and store its Gitea PAT as the Actions **secret** `RENOVATE_TOKEN`. Until it -exists, the nightly job fails loud (and, like the other secrets, a `GITEA_` prefix is -rejected). Also store a **scopeless** (read-only) github.com PAT as the secret +exists, the nightly job fails loud (and, like the other secrets, a `GITEA_`/`GITHUB_` +prefix is rejected). Also store a **scopeless** (read-only) github.com PAT as the secret `RENOVATE_GITHUB_TOKEN` — the workflow hands it to Renovate as `GITHUB_COM_TOKEN`, so lookups of github.com-hosted deps (actions, Playwright, changelogs) run authenticated instead of tripping the anonymous 60-requests/hour limit.