GitHub Banned All CI for Our (OSS) Org Because of Bad Drive-By Contributors

7 points

2 hours ago

A few weeks ago, Github decided to disable all Github Actions (including self-hosted runners) access for our open source org (lightningdevkit) for some unknown reason. As some of us happen to work for a company with a large Github corporate account, we tried to escalate through our corporate reps, who informed us that the issue appeared to be some drive-by contributors who weren't org members being flagged for using Actions to do crypto-mining. As the org isn't technically in our corporate account, we then had to wait a few weeks to get a response back on getting unbanned...only to be told that we "appeared to have been taking part in activity which goes against" Github's ToS. They then listed some examples of ToS-violating activities, none of which we've done, and the org itself obviously wasn't running any kind of mining in CI.

As we'd already had plenty of reasons to move off of GitHub (downtime, a website that has gotten consistently slower due to massive increases in client-side JS without new features over the past decade, PRs that won't load once they get past 50 comments, contributors getting banned (without crypt-mining) leading to potentially-useful PRs getting black-holed, slow support, etc, etc), this is more of a warning for others than any kind of attempt to get help.

Of course Github is struggling these days with an influx in AI Agent accounts driving a huge increase in spam and other garbage, so I sympathize a lot with the folks over there. But none of that means we have to use the (historically excellent) free product they're offering, we can also...not.

For those who weren't aware, codeberg/self-hosted forgejo can import entire github repos including historical issues and PRs, comments, etc.

1 comment

1 comment