13 ms·

This recent post that made it to the front page talks a lot about approaches GitHub has taken over its history: https://cursor.com/blog/git-at-any-scale https:

• mbreese 22d ago
  I ended up finding my own answer (after reading the above). https://nesbitt.io/2026/02/26/git-in-postgres.html https://nesbitt.io/2026/02/26/git-in-postgres.html Following another recent theme, the answer for Forgejo seems to be - just use Postgres.
  • jeremyjh 22d ago
    That approach was mentioned in the Cursor article. If a KV cache like Redis is too slow for that to work with large repositories, I don't see how Postgres could possibly work.