01:12:10 GitHub support got back to me. I got banned, with no right to appeal. Because I had a test in the workflow that checked whether the RandomXv2 hash matched the expected hash. They understood it as me trying to mine. 🥲 01:12:34 Nice 01:13:09 A similar thing happened to me. You can likely get unbanned, you just have to harass support for over 5 months ;) 01:13:36 I think I was banned from February to July 01:14:09 GitHub still sucks though, and it would be good to move to alternative platforms 01:14:58 Any suggestions? 01:15:36 Maybe try contacting support from a different email address? 01:17:19 I think I'll just create another account and remove the workflows. Just leave the release builds. 01:20:30 or just dont pust 5 kabillion commits 01:20:52 i alwyays think it amusing when people push commits like it is the save button 01:21:53 running 40mins of mining workflows is an easy way to get banned 01:22:16 at least they responded, which confirms the suspicion about why people who are pushing to forked p2pool are getting banned for ci 01:22:44 The response is probably templated slop 01:22:46 essentially implies that the upatream repo is whitelisted 01:23:16 "Because I had a test in the workflow that checked whether the RandomXv2 hash matched the expected hash. They understood it as me trying to mine. " 01:23:39 this doesnt seem like templates slop, it seems like a rare legit reason given my a human 01:23:45 by* 01:46:59 It wasn't 40 minutes of mining. 40 minutes was the build for Windows/Linux/Mac. 01:47:10 The test I mentioned was just a hash. They sent me a template email anyway. 01:48:25 https://mrelay.p2pool.observer/p/qfr_xacLRURJTWph/1.txt (code snippet, 5 lines) 01:48:47 Yes, that's the same email I got over 30 times 01:48:52 You might be cooked 01:58:52 @thesimstoshi:matrix.org: so they didnt say anything about mining? 02:08:12 They sent me that text from the email I mentioned above and this link. 02:08:12 https://docs.github.com/site-policy/github-terms/github-terms-for-additional-products-and-features#actions 02:10:17 I know that's what it was because I had just added the RandomX V2 hash test. 02:14:24 “Cryptomining;” “RandomX V2 hash test” 02:14:24 that’s the reason :p 02:14:45 this xd > <@ofrnxmr:xmr.mx> "Because I had a test in the workflow that checked whether the RandomXv2 hash matched the expected hash. They understood it as me trying to mine. " 06:28:38 new repo https://github.com/Zycord/zycord-node 09:56:14 My whole account's CI was banned in July 2025 too, because of P2Pool CI jobs, or maybe because I ran them while connected through VPN. It took a month or so to get CI back. 10:26:36 i got banned because I'm using Tor to access my GitHub account. Took a week 10:27:09 I bet support response time depends heavily on ban reason 12:45:12 <321bob321> I got banned for use SL email and got told to use a real email, whilst we went back and forth in email chain 12:58:26 lol