@phnt @TeaTootler @m0xEE @p


> Imagine not knowing how to use git.

does not compute.

> It's a collection of small bug fixes they didn't backport from upstream that drove me crazy.

do you have a list besides what you listed here? i maintain my own fork and can bring them forward.

> 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.

interesting that people use this for work. i think forgejo is a bit behind since they are volunteers and not paid coders

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

i saw this too, but i only mirror one repo so it wasn't a big problem.

> 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.

it sounds like default behavior is to pull in repo attrs like actions_enabled: true is that what you mean? i disabled actions on my system since it's not very mature. i used woodpecker which is fine atm.

> 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).

i can understand how this might be an issue for work/business. my business is just get shit done and hack everything. i have the luxury of laughing at licensing.