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.
An early implementation is available in Google Chrome (video demo). Essentially, you ask the browser, “Hey, can you give me a credential for an account at this Provider?” and as long as you've authenticated at that Provider's authorization servers, you'll be presented a list of your accounts to choose from by the browser, without leaving the page, and then you're authenticated!
。业内人士推荐新收录的资料作为进阶阅读
Here are the best Mar10 2026 deals we've seen so far:
В стране БРИКС отказались обрабатывать платежи за российскую нефть13:52
Россия вышла из соглашения с ООН14:29