summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormo8it <mo8it@proton.me>2024-03-27 17:08:38 +0100
committermo8it <mo8it@proton.me>2024-03-27 17:08:38 +0100
commit971e7f94dc58b6846e3b4e7f3d5df5b4ea72790b (patch)
tree3c53b2aed3bd8821ae0292eae90c936cfe5c43aa
parente7bb832bf3e651f88fa3318df7e6b04b56fb9dee (diff)
Update the link to conventionalcommits.org
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d66e3de..4fc7fb7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -65,7 +65,7 @@ changes. There's a couple of things to watch out for:
#### Write correct commit messages
-We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
+We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
specification.
This means that you have to format your commit messages in a specific way. Say
you're working on adding a new exercise called `foobar1.rs`. You could write