Choose Bash features or POSIX portability on purpose
Choose and document an interpreter target for shell scripts based on runtime environment and needed language features.
Interpreter mismatch A script marked #!/bin/sh uses arrays and [[ ]]. It passes locally but fails in a Debian-based CI container. The script promised POSIX but used Bash. Runtime contract Runtime first -> features second -> test with that shell Do not decide portability after writing the syntax. The interpreter target determines what language you are allowed to use. works here accidental interpreter behavior The script's promise matches its syntax and runtime. Portability is a requirement to verify, not an aesthetic label. 01 Runtime 02 Features 03 Proof Where will this run? The script will run in a controlled CI…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in