mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
| .. | ||
| build-ci-deps.yml.jinja | ||
| build-deb-repo.yml.jinja | ||
| build-macos-repo.yml.jinja | ||
| build-onedir-repo.yml.jinja | ||
| build-packages.yml.jinja | ||
| build-repos.yml.jinja | ||
| build-rpm-repo.yml.jinja | ||
| build-src-repo.yml.jinja | ||
| build-windows-repo.yml.jinja | ||
| ci.yml.jinja | ||
| layout.yml.jinja | ||
| nightly.yml.jinja | ||
| README.md | ||
| release.yml.jinja | ||
| scheduled.yml.jinja | ||
| staging.yml.jinja | ||
| test-salt-pkg-repo-downloads.yml.jinja | ||
| test-salt-pkg.yml.jinja | ||
| test-salt.yml.jinja | ||
| trigger-branch-workflows.yml.jinja | ||
| workflow-requirements-check.yml.jinja | ||
Workflow Templates
The templates are used to generate the actual workflows that run on GitHub Actions. They use Jinja2 as the template engine.
To Note
Let's try to keep the Jinja usage to the bare minimum because, as time passes, the complexity just piles up making it harder to read and interpret the templates.
Changes To Default Jinja Syntax
By default Jinja uses {% ... %}, {{ ... }}, {# ... #}, etc to do it's magic.
In order not to clash with the GitHub Actions syntax, and to also avoid having to
add bunch of {% raw %} ... {% endraw %} blocks, we changed some things:
- Instead of
{%and%}use<%and%> - Instead of
{{and}}use<{and}>
The rest of Jinja2 defaults apply.