Forgejo stores issues, pull requests, users, permissions, webhooks, branch protection rules, and CI status in Postgres already, and git repositories are the one thing left on the filesystem, forcing every deployment to coordinate backups between them, and the two systems scale and fail in different ways. The codebase already shows the strain: Forgejo mirrors branch metadata from git into its own database tables (models/git/branch.go) so it can query branches without shelling out to git every time.
2 days agoShareSave
。爱思助手下载最新版本是该领域的重要参考
tasks = append(tasks, t)，更多细节参见51吃瓜
Цены на нефть взлетели до максимума за полгода17:55，详情可参考体育直播
Украинцам запретили выступать на Паралимпиаде в форме с картой Украины22:58