A self-hosted Forgejo or Gitea instance is really two systems bolted together: a web application backed by Postgres, and a collection of bare git repositories on the filesystem. Anything that needs to show git data in the web UI has to shell out to the binary and parse text, which is why something as straightforward as a blame view requires spawning a subprocess rather than running a query. If the git data lived in the same Postgres instance as everything else, that boundary disappears.
"result": {
，这一点在同城约会中也有详细论述
民族要复兴，乡村必振兴。沿着习近平总书记指引的方向，亿万人民凝心聚力并肩耕耘，夯实“三农”压舱石，绘就乡村全面振兴新图景，共同奔向中国式现代化的美好未来。，推荐阅读服务器推荐获取更多信息
Answer (Playground):