2 SC1063

Joachim Ansorg edited this page 2022-10-31 15:10:50 +01:00

Table of Contents

• You need a line feed or semicolon before the do.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

You need a line feed or semicolon before the do.

Problematic code:

for file in * do
  echo "$file"
done

Correct code:

for file in *; do
  echo "$file"
done

# or 

for file in *
do
  echo "$file"
done

Rationale:

ShellCheck found a do on the same line as a loop, but do only starts a loop block at the start of a line/statement. Make the do the start of a new line/statement by inserting a linefeed or semicolon in front of it.

Exceptions:

If you wanted to treat do as a literal string, you can quote it to make this clear to ShellCheck and humans:

for f in "for" "do" "done"
do
  echo "Shell keywords include: $f"
done

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.