@jae @p @m0xEE @TeaTootler

>they're also shoving mcp into the system now for all the .ai worshippers
Imagine not knowing how to use git.

>forgejo isn't much better but im not sure what you mean its nearly unusable. ive got forgejo running fine for about a year. ci/cd is nearly always building and deploying for our our group.
It's a collection of small bug fixes they didn't backport from upstream that drove me crazy.

LDAP auth was broken for more than a month with a fix already in Gitea (maybe still isn't fixed). At work we depended on this, so I had to build custom images after every update.

Mirrors with LFS objects would seemingly randomly balloon in size. This one annoyed me for months until it got fixed in some release.

And lastly, after the addition of Forgejo actions, mirrors would start to have failing pipelines that got enabled automatically even though zero runners were configured. The solution was either manually go through 30 mirrors and disable actions manually for every repo, or completely disable actions in settings. The failing actions would be that big of a deal, if Forgejo cleaned them up properly from the DB. A fix for this with `gitea doctor` has been in upstream for 5 months and it still has not reached Forgejo v7.X which is the first affected version I think.

One day, I got fed up with Forgejo thanks Chinese scrapers downloading bundles and tarballs which created 30GB of orphaned archives, compared the Forgejo v7 and Gitea 1.21 (base for Forgejo v7) schemas and manually reverted the migrations. Did the same few days later at work and that solved all our problems I had with Forgejo. Plus the whole relicensing thing with Forgejo rubbed me the wrong way. They tried LibreOffice EEE and failed. Companies still prefer Gitea or even GitLab (we use both for reasons).