#630 The GitHub importer follows a renamed repository within the API
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#630
- pull request
- state:merged
GitHub answers a renamed repository's old name with a redirect to `/repositories/ /…`. The importer fetched with `redirect: 'error'`, so the catch-up docs/github.md gives for a renamed repository (`och-import-github --repo `, keeping the old IDs) failed with `fetch failed`. That happened on the hosted server during the move to circagraph.org, catching up `openchronology/timeline-app` → `circagraph/timeline-app`. - `GithubReader.get` now fetches with `redirect: 'manual'` and follows 301/302/307/308 itself, only within the API's own origin, up to five times. A redirect anywhere else is refused before the token is sent. - New test: a renamed repository is read through the redirect, IDs stay under the name given, and a redirect to another origin is refused. Checked against GitHub: a dry run of `--repo openchronology/timeline-app --since 2026-11-14` reads #623–#625 as `gh:openchronology:timeline-app:*`. Tests: the importer suites (github, forgejo, gitlab, branch view) pass locally: 39 tests. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/circagraph/timeline-app/pull/630
Related
Open #630 The GitHub importer follows a renamed repository within the API in the timeline