This may need a rendor to set params to config.jsonnet to replace the ${el-value} symbol. After replace the symbol then start anaysis the config to golang.
For example the a object define in jsonnet to collect all symbol from agola for the config usage, just like:
@huapox IMHO having a build config that changes its behavior based on the commit message look like a bad idea for many reasons (and if you’re using pull requests it won’t work when merging the PR since the commit message is not the one you’re expecting but something like Merge pull request #xx ...)