Hiya Hans
Its not possible to directly define GoCD templates as 'pipelines as code', assuming that is what you are referring to.
You could
- build custom automation triggers that update source controlled JSON templates via GoCD APIs
- or you could explore config repo plugins that better support templating conceptually (e.g Groovy, jsonnet - but come with their own downsides)
- or you could use an intermediary step to translate your templates to regular yaml|json config repo format
- write your own config repo plugin 😅