#626 A renamed repository's events keep the IDs of its former name
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#626
- pull request
- state:merged
Every GitHub item's ID includes its repository's name. Since `openchronology/timeline-app` became `circagraph/timeline-app`, the receiver on timescale.info ignores its deliveries (no route matches), and routing the new name would write every issue and pull request a second time under new IDs. A route can now name the repository's old name: ```json { "repository": "circagraph/timeline-app", "formerly": "openchronology/timeline-app", "timeline": "…" } ``` The receiver renames every repository a delivery names (each `full_name`) to the name its IDs use before reading it, so items, mentions and sub-issues are updated in place on the same timeline. `formerly` must be a single repository. The importer needs no change: given the old name, GitHub's API redirects to the renamed repository while no other repository takes that name (docs/github.md). After this is deployed, the production routes get `formerly`, and an import under the old name fills in the deliveries ignored meanwhile. Tests: `test/github-source.test.mjs` (a delivery from the new name writes the same IDs as one from the old), and the forgejo, gitlab, board and plan source tests. Its CI needs the org-move PR first (the CI image job still names ghcr.io/openchronology). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/circagraph/timeline-app/pull/626
Related
Open #626 A renamed repository's events keep the IDs of its former name in the timeline