Files
helm-gitea/.gitea
volker.raschekandCopilot 6821e792b2
Bash / bash-unittest (push) Successful in 14s
Bash / shellcheck (push) Successful in 20s
changelog / changelog (push) Successful in 15s
Helm / helm-lint (push) Successful in 16s
Helm / helm-unittest (push) Successful in 32s
ci: check the shell scripts with shellcheck
The chart ships shell scripts into the init containers, where a quoting or exit code bug surfaces as a broken
deployment rather than as a failing test. The bats suite covers the behaviour of config_environment.sh, but not the
classes of defects a static analyser catches, so shellcheck runs alongside it now.

The action is pinned to a commit sha, as the other actions of this workflow already are. Note that the tag is named
`2.0.0` and not `v2.0.0`, so the version comment deviates from the usual `# v<version>` form.

Submodules are deliberately not checked out. The action scans the whole working directory, and bats-core alone would
contribute several hundred files that are not ours to fix.

Co-authored-by: Copilot <copilot@github.com>
2026-10-03 20:31:12 +02:00
..