> we have self-hosted runners running behind our firewall and even those go down for these kinds of outages
Sounds like it's not as self-hosted as you think, or you have some other unnecessary dependency on something here? As long as GitHub isn't the sole place for your SCM, why would your self-hosted CI runners go down just because GitHub goes down?
I see, you're still using GitHub for SCM? Then I understand why it stops working :P When I said "Forgejo + their built-in Actions stuff" I meant you use Forgejo for git too, not just self-hosting runners but then connecting them to someone else's infrastructure.
If you're already hosting the runners, why not host git too? It's even simpler than running your own workers/runners.
Sounds like it's not as self-hosted as you think, or you have some other unnecessary dependency on something here? As long as GitHub isn't the sole place for your SCM, why would your self-hosted CI runners go down just because GitHub goes down?