Skip to content

Instantly share code, notes, and snippets.

@wxiaoguang

wxiaoguang/codeberg-reply.md

Last active June 20, 2025 10:47
Show Gist options
  • Save wxiaoguang/8a9774993e0531066b3d4d5377ada2b8 to your computer and use it in GitHub Desktop.
Save wxiaoguang/8a9774993e0531066b3d4d5377ada2b8 to your computer and use it in GitHub Desktop.
Download ZIP
codeberg-reply.md
Raw
codeberg-reply.md

@earl-warren wrote:

It is of course a lot less work for a quick implementation with no tests, but that won't be merged in Forgejo.

I hope you can stop from making more lies to Gitea.

The truth is Gitea has many well-tested PRs and features, if you take a look about Gitea 1.23/1.24 releases, you can see there is no more regressions than Forgejo, while Gitea has much more unique features, especially for self-hosted usages.

But if you follow Forgejo's development, you can see many tests are just useless or wrong. And there are even more regressions including security vulnerabilities. (for example: the Forjoge's Sync Fork feature introduced XSS, no Forgejo people realized that, eventally I helped to point out).

And I am sure there are still other security vulnerabilities in Forgejo including destorying some data.

If you have difficult to remember the history and details, I am still glad to remind what really happened from time to time. Since my account and comment will be deleted eventally, the GitHub gist is here: https://gist.github.com/wxiaoguang/8a9774993e0531066b3d4d5377ada2b8

And let's review what happened in history and why Gitea doesn't accept buggy PRs from some Forgejo people, Forgejo people just keep making lies about Gitea to make them look good.

  • They keeps criticizing Gitea community/maintainers and made a lot of lies, and they copied a lot of Gitea's feature and publicize that "they are their work" (for example: Gitea Actions, and more).

  • And be careful about their cherry-picks and PRs, I am sure there are not only one security problems, include XSS (some have been fixed), permission bypass, in their codebase but not in Gitea.

  • They keeps making false statements, for example: go-gitea/gitea#27455 (comment) , for the contributing guideline, it has been there for 7 years, they have been kindly warned not only one time, but they keeps saying that "Oh I don't know" and try to catch every chance to criticize Gitea.

  • They keeps claiming that "their test is good" but "Gitea merge large untested code", but their PRs to Gitea didn't have tests, eg: go-gitea/gitea#27753 and go-gitea/gitea#26841, and there are even more. There was no test, and even worse, they are incorrect.

And here are why many of theirs PRs to Gitea were not merged mainly because there are bugs and they do not respond.

Let's see why some of them are not merged (I only picked some my reviews):

Really suggest everyone to take a deep look ........

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment