Tod is a command line tool to test/debug OneDev CI/CD jobs against local changes to avoid the modify/commit/push/run/check cycles.
Under the hood, tod stashes local changes to a commit and pushes to server under a temporal ref to run specified job. Log of running job is streamed back to tod so that you can check job progress and status without leaving terminal.
Since job runs on server, it does not have many quirks and limitations of other tools (gitlab-runner exec or nektos/act for instance), such as requiring you to set up job environments, unable to handle job dependencies, etc. And you can still get fast feedback via shallow clone and cache.
My main gripe was that it was postet by OP as a "Show HN" ;)
Nice work btw always astounded how you keep developing it for so long nearly solo. I was many times intrigued enough to try to switch to OneDev just to try it, but my personal git setup is working too well right now. Never switch a running system runs too deep in me.
Anyway there seem to be discussions taking place so I will cut the noise and stop whining.
Under the hood, tod stashes local changes to a commit and pushes to server under a temporal ref to run specified job. Log of running job is streamed back to tod so that you can check job progress and status without leaving terminal.
Since job runs on server, it does not have many quirks and limitations of other tools (gitlab-runner exec or nektos/act for instance), such as requiring you to set up job environments, unable to handle job dependencies, etc. And you can still get fast feedback via shallow clone and cache.
For details, please check tod project at https://github.com/theonedev/tod