bug: CI does not work self-hosted nor outside of GitHub #753

New issue

Open

opened 2025-04-15 00:29:21 +00:00 by nex · 0 comments

nex commented

2025-04-15 00:29:21 +00:00

Owner

The CI workflows are currently dependent on Strawberry's self-hosted runner, and don't work outside of a GitHub worker environment. This will need fixing before we can use CI.

The org now has a (low performance) forgejo worker provided by myself, so hopefully getting CI into a fixed state shouldn't take too long and can work without me.

this commit diff may be relevant to see if we can reverse the self-hosted exclusiveness.
As for removing the GitHub dependency, we may need to get creative.

The CI workflows are currently dependent on Strawberry's self-hosted runner, *and* don't work outside of a GitHub worker environment. This will need fixing before we can use CI. The org now has a (low performance) forgejo worker provided by myself, so hopefully getting CI into a fixed state shouldn't take too long and can work without me. [this commit diff](https://forgejo.ellis.link/continuwuation/continuwuity/commit/7c17163730fcd0f43132cce82cc28b6793ae662a?style=unified&whitespace=show-all&show-outdated=) may be relevant to see if we can reverse the self-hosted exclusiveness. As for removing the GitHub dependency, we may need to get creative.