From 93355ee143a9328591419b67e1f0ade6989026c0 Mon Sep 17 00:00:00 2001 From: S Date: Sun, 1 Mar 2026 10:02:35 -0500 Subject: [PATCH] docs: update USAGE_GUIDE.md for single GitHub token Consolidated two tokens into one GITHUB_TOKEN with repo scope. Co-Authored-By: Claude Opus 4.6 --- USAGE_GUIDE.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/USAGE_GUIDE.md b/USAGE_GUIDE.md index f8b18fe..2193d6f 100644 --- a/USAGE_GUIDE.md +++ b/USAGE_GUIDE.md @@ -33,14 +33,11 @@ Before running anything, confirm: ### 2. GitHub Tokens -You need two GitHub Personal Access Tokens: +You need one GitHub Personal Access Token: | Token | Scope | Used By | |-------|-------|---------| -| `GITHUB_TOKEN` | `repo` (read) | Preflight validation, repo migration | -| `GITHUB_MIRROR_TOKEN` | `repo` (read+write) | Push mirrors from Gitea to GitHub | - -These can be the same token if it has write scope. +| `GITHUB_TOKEN` | `repo` (read+write) | Migration, push mirrors, preflight validation | ### 3. Configuration @@ -199,7 +196,7 @@ When resuming from a later phase, Gitea is already running on ports 3000. Use: **Symptom**: API calls fail with HTTP 401. -**Fix**: Generate a new token on GitHub, update `GITHUB_TOKEN` (and/or `GITHUB_MIRROR_TOKEN`) in `.env`, then re-run the failed phase. +**Fix**: Generate a new token on GitHub, update `GITHUB_TOKEN` in `.env`, then re-run the failed phase. ### Large repos time out during migration