privacy-in-design/gitea-migration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update USAGE_GUIDE.md for single GitHub token

Browse Source 
Consolidated two tokens into one GITHUB_TOKEN with repo scope.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
S
2026-03-01 10:02:35 -05:00
parent 017ab098f1
commit 93355ee143
1 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
USAGE_GUIDE.md
View File

@@ -33,14 +33,11 @@ Before running anything, confirm:
### 2. GitHub Tokens ### 2. GitHub Tokens
You need two GitHub Personal Access Tokens: You need one GitHub Personal Access Token:
| Token | Scope | Used By | | Token | Scope | Used By |
|-------|-------|---------| |-------|-------|---------|
| `GITHUB_TOKEN` | `repo` (read) | Preflight validation, repo migration | | `GITHUB_TOKEN` | `repo` (read+write) | Migration, push mirrors, preflight validation |
| `GITHUB_MIRROR_TOKEN` | `repo` (read+write) | Push mirrors from Gitea to GitHub |
These can be the same token if it has write scope.
### 3. Configuration ### 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. **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 ### Large repos time out during migration