From fa5f7da5c4d0a91c173ddbce60afea4aefcbbc2d Mon Sep 17 00:00:00 2001 From: Arunavo Ray Date: Wed, 22 Oct 2025 23:53:30 +0530 Subject: [PATCH] updated article --- www/src/pages/use-cases/backup-github-repositories.mdx | 4 ++-- www/src/pages/use-cases/preserve-github-history.mdx | 2 +- www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/www/src/pages/use-cases/backup-github-repositories.mdx b/www/src/pages/use-cases/backup-github-repositories.mdx index ff53f5b..08115e2 100644 --- a/www/src/pages/use-cases/backup-github-repositories.mdx +++ b/www/src/pages/use-cases/backup-github-repositories.mdx @@ -14,7 +14,7 @@ GitHub is great—right up until an outage, SSO change, or account lockout stran ## Requirements - Docker Engine and Compose on the host that will run the mirror -- A GitHub personal access token with `repo`, `read:org`, and `admin:org` if you mirror orgs +- A GitHub personal access token (classic) with `repo`, plus the `read:org` checkbox under `admin:org` when you mirror organizations (leave the write/admin boxes unchecked) - A self-hosted Gitea instance (can be on the same box) and admin or org owner credentials - Open ports 4321 (web UI) and 3000 (default Gitea) inside your network @@ -41,7 +41,7 @@ Wait for "Server started" before moving on. ### 2. Generate tokens and connect GitHub -1. Create a GitHub personal access token (classic) with at least `repo`, `read:org`, and `admin:org` if you want organization mirrors. +1. Create a GitHub personal access token (classic) with `repo` enabled and, inside the `admin:org` section, check `read:org` so the mirror can list organization repositories—leave `write:org` and `admin:org` unchecked. 2. Log in to Gitea and create an access token for an admin/owner account with `write:repository`. 3. Visit `http://:4321` and sign up—the first user becomes admin. 4. Complete the setup wizard: diff --git a/www/src/pages/use-cases/preserve-github-history.mdx b/www/src/pages/use-cases/preserve-github-history.mdx index 12b3f0f..306dd52 100644 --- a/www/src/pages/use-cases/preserve-github-history.mdx +++ b/www/src/pages/use-cases/preserve-github-history.mdx @@ -14,7 +14,7 @@ GitHub accounts get banned, repos go private, and owners rage-delete history. If ## Requirements - Running Gitea Mirror (follow the [backup playbook](../backup-github-repositories/)) -- GitHub PAT with metadata scopes (`repo`, `read:org`) +- GitHub PAT with `repo` enabled (add the `read:org` checkbox under `admin:org` when you archive organization repositories; leave write/admin unchecked) - Destination Gitea with enough disk for cloned repos + attachments - Optional: object storage or snapshots for long-term archiving of the mirror volume diff --git a/www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx b/www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx index e863d04..daa14a4 100644 --- a/www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx +++ b/www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx @@ -14,7 +14,7 @@ You may still collaborate on GitHub every day, yet want a LAN Gitea copy you con ## Requirements - Gitea Mirror deployed (Docker, Proxmox LXC, or Helm) -- GitHub PAT with `repo`, `read:org`, and `admin:org` scopes +- GitHub PAT with `repo` enabled (add the `read:org` checkbox under `admin:org` to mirror organizations; leave write/admin unchecked) - Gitea API token for the target account/org - Stable connectivity between the mirror host and both GitHub + Gitea