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.
Maintained by Dimitris Papailiopoulos (@dimitrispapail).
，详情可参考WPS官方版本下载
const hash = await computeHash(forHash);
Another possibility could be for supporting local development flows. Throughout the development of Towerborne, we struggled to find the best approach for this. Flaky backend development environments can have a real impact on content creators who need things up and running to do their work. At the same time, backend engineers need to roll out new features quickly leading to some inevitable friction. One can imagine an approach that gives people the option to use the Native AOT DLL when running the game through the Unreal editor, but interacts with a real backend when running an actual game build.