Wish a git forge would support both Actions and Gitlab CI pipelines. Reuse community workflows for simple actions, default to Gitlab CI for anything custom.
the way the CI runners on tangled work, you could just plug in your own bespoke runner as long as it fits the interface. we implement two such "engines": nixery and microvm. you can plug an engine like tack[0], which can act like a bridge interface to other CI systems. there is also loom[1], which is a kubernetes based engine.
the way the CI runners on tangled work, you could just plug in your own bespoke runner as long as it fits the interface. we implement two such "engines": nixery and microvm. you can plug an engine like tack[0], which can act like a bridge interface to other CI systems. there is also loom[1], which is a kubernetes based engine.
[0]: https://tangled.org/mitchellh.com/tack
[1]: tangled.org/evan.jarrett.net/loom