circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

Answer large forks at once and copy their index afterwards

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

A fork or duplicate of 20,000 moments and durations or more commits with its shared history, settings and charge, marked as being prepared, and its index is copied after answering: in one background transaction from one snapshot of the source, a page of rows per statement, brought back to the forked revision if the source saved since (or rebuilt from it when that cannot be done in place or the source is gone). Until ready, its index answers 409 and its platform page waits for it; restarts resume unprepared copies. At 200,000 moments a fork is answered in 0.06 s and ready about 33 s later. Part of #145. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/f2c5941f77f4e5984b3ec52f31d114943aa72ed6

Related

Open Answer large forks at once and copy their index afterwards in the timeline

Answer large forks at once and copy their index afterwards