Files
Zach Kellingandzeekay 6153981603 oss: the year is the forge's, every repository counted once
The year of commits was GitHub's stats/commit_activity for public,
non-fork repositories: one call each, some 2,100, more than the deploy
token's hourly allowance, so a push never refreshed it and the private
two-thirds of the estate were never in it.

The forge now mirrors every repository of every org the estate publishes
under (universe estate.json), and cloud serves what its index counts at
GET /v1/git/activity.  sync-oss reads that once a build:

- the year is our commits, by SHA, across every repository, private ones
  counted and never named; a carried project's upstream history is in
  estate.commits and heads nothing
- the days, the newest commits (linked to GitHub where GitHub publishes
  the repository, else the forge), each org's commits and every forge
  link come from the same read
- each group's orgs are rewritten from the estate's list
- GitHub still answers what only it knows: public names, stars, forks,
  languages, homepages, contributors

The forge card shows the whole estate when the snapshot carries it, and
/oss/<org> its org as the forge holds it.  Until cloud serves the read,
or when it answers a partial year, the committed snapshot stands.
2026-10-30 07:55:43 -07:00
..