From 66a30d61cf1b58ca74f712d50b589fe1018863f3 Mon Sep 17 00:00:00 2001 From: Sven van Heugten Date: Wed, 4 Mar 2026 07:03:47 +0100 Subject: [PATCH] Fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2d8c3f8..3eb57c4 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ dotnet test --no-build ``` ~~~ -This script will be run with `set -euo pipefail`, and the commit will be considered correct if the script exits succesfully. +This script will be run with `set -euo pipefail`, and the commit will be considered correct if the script exits successfully. You can technically assert that a command fails by writing `! ... || exit 1`, or write assertions about a command's output by piping it to `grep`, but doing so won't lead to very useful error messages when things go wrong. To make those things easier, there are some helper functions included, which are inspired by [bats](https://github.com/bats-core/bats-core) and [bats-assert](https://github.com/bats-core/bats-assert):