Content-level diffs, three-way merge, and blame stay in libgit2 rather than being reimplemented in SQL, since libgit2 already has that support and works against the Postgres backends through cgo bindings. The Forgejo fork would be “replace modules/git with libgit2 backed by Postgres” rather than “replace modules/git with raw SQL,” because the read-side queries only cover the simple cases and anything involving content comparison or graph algorithms still needs libgit2 doing the work with Postgres as its storage layer. That’s a meaningful dependency to carry, though libgit2 is well-maintained and already used in production by the Rust ecosystem and various GUI clients. SQL implementations of some of this using recursive CTEs would be interesting to try eventually but aren’t needed to get a working forge. The remaining missing piece is the server-side pack protocol: the remote helper covers the client side, but a Forgejo integration also needs a server that speaks upload-pack and receive-pack against Postgres, either through libgit2’s transport layer or a Go implementation that queries the objects table directly.
Save up to $300 or 30% to TechCrunch Founder Summit
，推荐阅读heLLoword翻译官方下载获取更多信息
据新华社伦敦2月26日电 （记者郭爽、高文成）总部位于英国伦敦的品牌估值机构品牌金融公司26日发布的《科技品牌100强》报告显示，中国科技品牌总价值增长强劲，在“科技与创新国际认知”排名中居全球第一。
Within JS ORM picks only