Mathieu Fenniak

@Gusted@social.linux.pizza A company going full AI, while also "retiring" their company values, feels like it should be satire and not reality.

@vsp@mastodon.world @linkedin@mastodon.social I'm qualified to be the Assistant to the Deputy Chief. 🤔 Perhaps that's the misunderstanding.

@Philip@social.simplexity.quest As a Forgejo expert, I can answer this. 🙂 Worktree runs Gitea, not Forgejo. Likely forked Gitea and changed, as the reported version number wouldn't reflect a Gitea release that contains the same capabilities that Worktree has. Oddly Worktree is not Open Source, https://worktree.ca/worktree -- no repo for Worktree itself. 🧐

@vga256@mastodon.tomodori.net I'd be very interested in reading it. Even more if it was possible to include some first-hand information, maybe from interviews, about why some things work the way they do (in addition to the obvious like technical constraints).

@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.

@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.