Do you think we should merge this then I open another PR for a new test deployment server or even not use that kind of testing in future?
This is deffo WIP. Looking for input!
Do you think we should merge this then I open another PR for a new test deployment server or even not use that kind of testing in future?
This is deffo WIP. Looking for input!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is part of #61
Do you think we should merge this then I open another PR for a new test deployment server or even not use that kind of testing in future?
This is deffo WIP. Looking for input!
- compose.matrix.yml: add trailing newline - compose.ftp-222*.yml: fix YAML indentation (8->6 spaces) - entrypoint.sh.tmpl: fix SC2198 ([ -n "$@" ] -> [ $# -gt 0 ]) - All .tmpl files: migrate from {{ env }} to {{ getenv }} for gomplate v5 compat - uploads.ini.tmpl: add {{- / -}} whitespace trimming, fix double-space typo - tests/run.sh: only run ShellCheck on *.sh.tmpl files - tests/test_shell.sh: gracefully skip if shellcheck not installed - tests/test_templates.sh: remove dead render() function, gracefully skip if gomplate not found, use set -a/. for env sourcing - tests/test_compose_config.sh: validate override files combined with compose.yml, skip partial snippets needing more context - README.md: add test instructions with brew installa9efe706d1toe14f47a4b3Just FYI, these tests were generate by LLM: OpenCode Zen BigPickle model