Post #2148579
2026-05-06 18:11 UTC
Replies (8)
-
@mahryekuh@hachyderm.io 2026-05-06 18:13
@hugovk@mastodon.social Oof, that is rough timing with the outage. HugOps to the team pulling this off, especially under difficult circumstances!
-
@danielquinn@mastodon.social 2026-05-07 00:10
@hugovk@mastodon.social Please just stop using GitHub already!
-
@valorzard@mastodon.gamedev.place 2026-05-07 01:36
@hugovk@mastodon.social this might be a bit off topic, but is there a good place to follow along with JIT development?
-
@nojhan@social.antigene.org 2026-05-07 05:51
@hugovk@mastodon.social When is the move to self-hosting planned?
-
@kura@hai.z0ne.social 2026-05-07 17:18
@hugovk@mastodon.social get away from GH. use GH as a mirror, if at all.
-
@kura@hai.z0ne.social 2026-05-07 17:18
@hugovk@mastodon.social get away from GH. use GH as a mirror, if at all.
-
@mirabilos@toot.mirbsd.org 2026-05-07 17:25
@hugovk@mastodon.social well it’s Microslop GitHub, you get to lie in the bed you chose
-
@eschwartz@fosstodon.org 2026-05-07 17:41
@hugovk@mastodon.social the writing has been on the wall for a long time. Shockingly it turns out that #GitHub uptime isn't really better than #codeberg anymore, so the only really good excuse to keep using GitHub is if you're hugely reliant on free CI minutes. I sympathize and am in the same boat. I have been wondering for a bit, if it might be viable to have some simple automation that mirrors any PRs on codeberg to GitHub just to run CI, then report back on codeberg.