Closed sbernauer closed 7 months ago
Name | Link |
---|---|
Latest commit | e331ef6645c39c98c56717731291210b54fdbf9d |
Latest deploy log | https://app.netlify.com/sites/stackable-docs/deploys/6613a480dd2b2600083f646a |
Deploy Preview | https://deploy-preview-579--stackable-docs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Can we pull out the branches into a var '[main, 23.11, ...]'and override that with '[main]' for the dev only run, instead of duplicating the entire playbook?
What var are you referring to? yaml anchors or is this an Ansible playbook? Looking at https://docs.antora.org/antora/latest/playbook/ I can't find any concept of variables.
I think I would prefer yaml anchors anyway and we could do some yq
magic in the Makefile
It's possible to specify (Just realized that it only works if all sources have the same branches, and that's not the case)content.branches
directly: https://docs.antora.org/antora/latest/playbook/configure-content-sources So you don't have to configure branches per source and you don't have to use the anchors.
~~What do you mean with a var though? @soenkeliebau ~~
What do you mean with a var though? @soenkeliebau
I was being stupid and mistook this for Ansible :(
Thanks for the review!
To speed up feedback loop