mirror of
https://github.com/git/git
synced 2024-08-27 11:39:22 +00:00
832c68b3c2
There are quite a few tests which print an error messages and then explicitly signal failure with `false`, `return 1`, or `exit 1` as the final command in an `if` branch. In these cases, the tests don't bother maintaining the &&-chain between `echo` and the explicit "test failed" indicator. Since such constructs are manually signaling failure, their &&-chain breakage is legitimate and safe -- both for the command immediately preceding `false`, `return`, or `exit`, as well as for all preceding commands in the `if` branch. Therefore, stop flagging &&-chain breakage in these sorts of cases. Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
11 lines
190 B
Plaintext
11 lines
190 B
Plaintext
# LINT: broken &&-chain okay if explicit "false" signals failure
|
|
if condition not satisified
|
|
then
|
|
echo it did not work...
|
|
echo failed!
|
|
false
|
|
else
|
|
echo it went okay
|
|
congratulate user
|
|
fi
|