1

SC2239

Vidar Holen edited this page 2018-10-17 20:38:59 -07:00

Table of Contents

• Ensure the shebang uses the absolute path to the interpreter.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

Ensure the shebang uses the absolute path to the interpreter.

Problematic code:

#!bin/sh
echo "Hello World"

Correct code:

#!/bin/sh
echo "Hello World"

Rationale:

The script's interpreter, as specified in the shebang, does not start with a /.

The interpreter should always be specified by absolute path to ensure that the script can be executed from any directory. When it's not, it's generally a typo like in the problematic example.

If you don't know where the interpreter is and you hoped to use #! bash, this is not an option. Use /usr/bin/env instead:

#!/usr/bin/env bash
echo "Hello World"

While not required by POSIX, env can essentially always be found in /usr/bin and will search the PATH for the specified executable.

Exceptions:

None.

Related resources:

• Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!

ShellCheck

• Installation

  • CentOS6
  • More Installation Guides

• Usage

  • Directive
  • Ignore

• Integrating and extending

  • Misc. contributions
  • Azure Pipelines
  • Buildkite
  • CircleCI
  • DevGuide
  • Integration
  • JUnit
  • Phabricator
  • TravisCI
  • GitLab CI
  • Drone
  • GitHub Actions

• Severity

• Template

Each individual ShellCheck warning has its own wiki page like SC1000. Use GitHub Wiki's "Pages" feature above to find a specific one, or see Checks.

<--- This is a global footer, please don't edit it. --->