svenvanheugten/git-check-assertions
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update article name

Browse source
This commit is contained in:
Sven van Heugten 2026-03-13 06:14:57 +01:00
parent 0cdf9a73c6
commit 1543d47f6e
No known key found for this signature in database
GPG key ID: D612F88666F4F660
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -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