Retire the GitHub repository to a read-only mirror #1713

Closed
opened 2026-10-29 12:24:30 +00:00 by sam · 1 comment
Owner

Push already lands on Gitea first and mirrors to GitHub. Nothing reads from GitHub.

Soft stage: disable issues, projects and wiki, and pull requests, in Settings ->
General -> Features (pull requests has no CLI or API, it is a UI checkbox only).
Hard stage: gh repo archive samcharles93/archie-core, then delete the GitHub pushurl
in the same breath --

git remote set-url --delete --push origin https://github.com/samcharles93/archie-core.git

An archived repository rejects pushes, so leaving the pushurl in place turns every
git push into an error on the mirror leg. --atomic is per remote: if the GitHub leg
fails, the command exits non-zero even though Gitea took everything.

Push already lands on Gitea first and mirrors to GitHub. Nothing reads from GitHub. Soft stage: disable issues, projects and wiki, and pull requests, in Settings -> General -> Features (pull requests has no CLI or API, it is a UI checkbox only). Hard stage: `gh repo archive samcharles93/archie-core`, then delete the GitHub pushurl in the same breath -- git remote set-url --delete --push origin https://github.com/samcharles93/archie-core.git An archived repository rejects pushes, so leaving the pushurl in place turns every `git push` into an error on the mirror leg. `--atomic` is per remote: if the GitHub leg fails, the command exits non-zero even though Gitea took everything.
sam added the mediumtask labels 2026-10-29 12:24:30 +00:00
sam self-assigned this 2026-10-29 12:24:30 +00:00
Author
Owner

Triaged: no code change is needed for this. No code change is needed. Issue 1713 asks for three actions that live outside this tree: two GitHub repository settings changes (Features checkboxes, then gh repo archive samcharles93/archie-core) and one machine-local git config change (git remote set-url --delete --push origin ...). None of them is repository content, and the repository already describes that end state.

What I checked:

  • CLAUDE.md:183 already states the policy: "GitHub is a read-only mirror; do not open, close or comment there." Issues are tracked on the Gitea primary (tea issues ... -r sam/archie), so nothing in the repo's working guidance depends on GitHub being writable.
  • No code or automation pushes to GitHub. install.sh hardcodes SOURCE_GIT="https://git.catlow.cloud/sam/archie.git" and DEFAULT_RELEASES="git.catlow.cloud/sam/archie"; release.yml pushes git push --atomic origin main <tag> and its own error text says to "dispatch the release from the Gitea primary"; deploy.yml, canary.yml and promote.yml log into git.catlow.cloud. RELEASING.md describes Gitea as the release home and treats a mirror as a copy that carries its own secrets — which stays true of an archived GitHub copy.
  • A tree-wide grep for raw.githubusercontent, github.com/samcharles93/archie-core.git, gh repo and "GitHub issues" found only CHANGELOG.md and docs/news/releases.json history (old install-command bullets from past releases), which are records and correctly not rewritten. The remaining github.com/samcharles93/archie-core hits are the Go module path, an identifier that does not require GitHub reads, plus the generic GitHub forge extension and docs/github-token.md, which are about connecting Archie to other GitHub repositories, not this one.

Two things in the issue body are operational cautions rather than defects to fix here: an archived repo still serves reads, so only pushes break, and that break is caused by the leftover pushurl (a local-config consequence), while --atomic is per remote, so a GitHub-leg rejection makes the exit non-zero after Gitea has already taken the refs. Both are settled by the issue's own sequencing — archive and delete the pushurl in the same breath.

Nothing to verify by test or gate, because there is no code behaviour involved. My verification was read-only inspection of the files named above; I did not run gh, check the live GitHub repository's state, or confirm the local remote configuration, since those are outside this tree and outside a read-only mission.

Triaged: no code change is needed for this. No code change is needed. Issue 1713 asks for three actions that live outside this tree: two GitHub repository settings changes (Features checkboxes, then `gh repo archive samcharles93/archie-core`) and one machine-local git config change (`git remote set-url --delete --push origin ...`). None of them is repository content, and the repository already describes that end state. What I checked: - CLAUDE.md:183 already states the policy: "GitHub is a read-only mirror; do not open, close or comment there." Issues are tracked on the Gitea primary (`tea issues ... -r sam/archie`), so nothing in the repo's working guidance depends on GitHub being writable. - No code or automation pushes to GitHub. install.sh hardcodes `SOURCE_GIT="https://git.catlow.cloud/sam/archie.git"` and `DEFAULT_RELEASES="git.catlow.cloud/sam/archie"`; release.yml pushes `git push --atomic origin main <tag>` and its own error text says to "dispatch the release from the Gitea primary"; deploy.yml, canary.yml and promote.yml log into `git.catlow.cloud`. RELEASING.md describes Gitea as the release home and treats a mirror as a copy that carries its own secrets — which stays true of an archived GitHub copy. - A tree-wide grep for `raw.githubusercontent`, `github.com/samcharles93/archie-core.git`, `gh repo` and "GitHub issues" found only CHANGELOG.md and docs/news/releases.json history (old install-command bullets from past releases), which are records and correctly not rewritten. The remaining `github.com/samcharles93/archie-core` hits are the Go module path, an identifier that does not require GitHub reads, plus the generic GitHub forge extension and docs/github-token.md, which are about connecting Archie to other GitHub repositories, not this one. Two things in the issue body are operational cautions rather than defects to fix here: an archived repo still serves reads, so only pushes break, and that break is caused by the leftover pushurl (a local-config consequence), while `--atomic` is per remote, so a GitHub-leg rejection makes the exit non-zero after Gitea has already taken the refs. Both are settled by the issue's own sequencing — archive and delete the pushurl in the same breath. Nothing to verify by test or gate, because there is no code behaviour involved. My verification was read-only inspection of the files named above; I did not run `gh`, check the live GitHub repository's state, or confirm the local remote configuration, since those are outside this tree and outside a read-only mission.
sam closed this issue 2026-11-06 22:19:28 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1713