I never suggested building everything from scratch. However, Forgejo is ultimately just a new dependency. Does abandoning GitHub Actions for Forgejo Actions eliminate lock-in? No, it’s merely a shift in dependency.

If the Forgejo core team announces tomorrow that their 'philosophy has changed' and overhauls the architecture, tens of thousands of 'independent' home servers will grumble, but they'll inevitably run git pull to update anyway. And eventually, they might migrate again. That cycle is inevitable, and I have no intention of denying it.

The issue in the context of this post is that it rejects dependency on GitHub while presenting Forgejo as the escape. If your defense is 'why reinvent the wheel,' you are essentially proving my point: we are just choosing a new center to depend on.

Beyond that, we might just be talking past each other at this point. I don't think you are wrong, and I have no intention of twisting your words. Your underlying point is likely this: GitHub's service quality has degraded, and with their aggressive AI strategies driving users away, it is strange to view the act of leaving negatively. I fully respect our difference of opinion there.

I honestly just got a bit annoyed earlier because you framed your reply as if I hadn't even read the article. Anyway, let's leave it at that. There is no reason to misrepresent your views, and no reason for us to argue further.