2026-07-15 04:23 UTC
@zerodogg@hachyderm.io Hm... you could put a repo on Codeberg that has the workflow files and use the workflow dispatch API to trigger jobs on-demand. But I don't know how you'd access your private self-hosted repos then -- Forgejo normally creates authentication tokens to allow `actions/checkout` to work, for example.
If you already have a self-hosted runners, self-hosted Forgejo is usually the easier part of that equation.
Replies (1)
-
@zerodogg@hachyderm.io 2026-07-15 09:18
@mfenniak@yyc.bike Thanks! I was thinking that access to checkout could be solved with a ssh key. Having a dummy repo on Codeberg does feel kind of like abusing the system though. The thing is that I don't really need any of the functionality Forgejo , other than CI. Everything that needs Forgejo is on Codeberg. The remainder is pretty much only a few private websites that there's no value in hosting publicly. I could write my own thing for it, I doubt it'd be very hard, I need almost nothing, but to me this sounds like something that should already be solved by someone else. But maybe most just use centralised forges with private repos.