Use of legacy backtick SH-2006
Anti-pattern
Major
a year ago
—
a year old
Use $(...) notation instead of legacy backticks
...32git commit -m "$release_note"
33
34# Sets the new remote
35git_remote=`git remote`36if [ "$git_remote" = "" ]; then # git remote not defined
37
38 if [ "$GIT_TOKEN" = "" ]; then
Description
Consider using the $(...) notation instead.
Backtick command substitution \...`` is legacy syntax with several issues.
* It has a series of undefined behaviors related to quoting in POSIX.
* It imposes a custom escaping mode with surprising results.
* It's exceptionally hard to nest.
$(...) command substitution has none of these problems, and is therefore strongly encouraged.
Problematic code:
echo "You are running on `uname`"
Preferred code:
echo "You are running on $(uname)"
Read more about it here:
- BashFq: Why is $(...) preferred over \...`` (backticks)?.