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.
Юрий Леонов (ведущий редактор отдела «Бывший СССР»)
，更多细节参见heLLoword翻译官方下载
“十五五”时期，我国发展环境面临深刻复杂变化：向内看，人口老龄化程度加深，资源环境等硬约束增强，传统经济增长动力逐步减弱；向外看，经济全球化遭遇逆流，世界经济增长乏力。
（一）盗窃、损毁、擅自移动铁路、城市轨道交通设施、设备、机车车辆配件或者安全标志的；