2026-07-15 09:18 UTC
@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.
Replies (1)
-
@mfenniak@yyc.bike 2026-07-15 13:20
@zerodogg@hachyderm.io Hm... you can use forgejo's runner as a CLI tool to run a workflow. But then how/when would you trigger it or run it? A git repo hook, maybe... but then it runs inline when you push, and the logs are gone when you're done. 🤔 Another step or two and you're basically at Forgejo anyway. It might be a good stopgap approach though because, in the future if you find your needs change and Forgejo is a better fit for your self-hosted side, you can still reuse the same workflows.