From 1543d47f6ea4d014d4c24ba9055e5de9b1c1bff0 Mon Sep 17 00:00:00 2001 From: Sven van Heugten Date: Fri, 13 Mar 2026 06:14:57 +0100 Subject: [PATCH] Update article name --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 51d6250..5f0e8da 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ I recently wrote two blog posts arguing that there might be some value in writing verifiable claims, i.e. assertions, inside of our commit messages: * [Should we start writing verifiable claims in commit messages?](https://sven.memcmp.org/2026-02-19-should-we-start-writing-verifiable-claims-in-commit-messages/) -* [Writing the steps to validate a test in the commit message](https://sven.memcmp.org/2026-02-20-writing-the-steps-to-validate-a-test-in-the-commit-message/) +* [Writing the steps to validate a test that already passes in the commit message](https://sven.memcmp.org/2026-02-20-writing-the-steps-to-validate-a-test-that-already-passes-in-the-commit-message/) This is a simple verifier for such assertions. @@ -128,7 +128,7 @@ assert_output --partial "Invalid URL" ``` ~~~ -Assert that a specific change breaks the tests (as discussed [here](https://sven.memcmp.org/2026-02-20-writing-the-steps-to-validate-a-test-in-the-commit-message/)): +Assert that a specific change breaks the tests (as discussed [here](https://sven.memcmp.org/2026-02-20-writing-the-steps-to-validate-a-test-that-already-passes-in-the-commit-message/)): ~~~ ```git-check-assertions