CodeBeaver VS Gitea

I just open-sourced CodeBeaver, a tool I built after LLM-generated code kept sneaking weird bugs into my projects.

It's on the radar (as Gitea is also actively working on this - https://github.com/go-gitea/gitea/pull/35295), but I suspect you can not expect anything for a while:

"Upstream Proposal: Repository Grouping/Subgroups in Forgejo":

https://codeberg.org/fedora/forgejo-deployment/issues/224

"feat: extend Forgejo URL structure from organisation/repository to organisation/project/repository":

https://codeberg.org/forgejo/forgejo/issues/9550

Here's an example off the top of my mind:

https://github.com/go-gitea/gitea/blob/main/go.sum

I bounced away from Gitea because they don't (last time I checked) have OIDC. I started[0] trying to revive-and-drive a previous PR[1] to add it, but the test failures are beyond my motivation to investigate and resolve.

[0] https://github.com/go-gitea/gitea/pull/33945

[1] https://github.com/go-gitea/gitea/pull/25664

It’s coming: https://github.com/go-gitea/gitea/pull/20311

I would be willing to guess that self hosting gitea as a backup mirror is less work than doing the same for Bluesky. But, just speculating

As I mentioned in a previous post - you can use "git" without Github by hosting an instance of the open-source Gitea service.

https://github.com/go-gitea/gitea

As mentioned in the last post, I keep my notes in git repositories. I originally used Obsidian for years as my note-taking application of choice after migrating away from Google Keep, using the vast library of community plugins (namely obsidian-livesync and obsidian-git) to back up and sync my notes on an interval to my 3 remotes; GitHub, my private Gitea instance for my private "second brain" type notes, and my Otterwiki instance (a wiki that runs on a git server of markdown files).

The solution to this is to use fake e-mails.

I can't say what Forgejo has over Gitea, but I can tell you Forgejo is missing everything from the 888 merged PRs in Gitea 1.23: https://github.com/go-gitea/gitea/releases/tag/v1.23.0-rc0

Repo license support, integrated Arch package repository, automatic issue suggestions, and the new review+homepage UIs would be notable ones for me.

See this issue: https://github.com/go-gitea/gitea/issues/1029

For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.