shell-conventions

Safe shell scripting conventions enforce strict mode usage, consistent quoting, trap-based cleanup, and a main() pattern to prevent accidental execution. These rules ensure reliability and portability across Bash and POSIX sh environments.

You can enforce shell script formatting and linting in CI pipelines by applying conventions that satisfy shellcheck rules for safety and shfmt for consistent style. This ensures portable code passes automated checks.

Yes, these shell conventions harmonize Bash and POSIX sh practices to ensure portability. They promote shellcheck-friendly code and enforce shfmt formatting for consistent style across teams.

To resolve the script directory reliably, these shell conventions enforce specific SCRIPT_DIR resolution patterns. This ensures your script correctly locates files relative to its own path across different execution environments.

The main() pattern in shell scripting encapsulates execution logic within a function, preventing accidental execution when the script is sourced. Use it in all new scripts to ensure safe sourcing.

Shell scripts fail when sourced because they lack a main() pattern and proper safety flags, causing accidental execution. Adopting trap-based cleanup and strict mode conventions prevents these errors.