From a75c6dbb7317d805383450d2fc9138f0dddbe9ed Mon Sep 17 00:00:00 2001 From: Garrit Franke Date: Sat, 20 Feb 2021 17:44:51 +0100 Subject: [PATCH] Fix date of post --- .../{2021-02-19-changelogs.md => 2021-02-20-changelogs.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/posts/{2021-02-19-changelogs.md => 2021-02-20-changelogs.md} (99%) diff --git a/content/posts/2021-02-19-changelogs.md b/content/posts/2021-02-20-changelogs.md similarity index 99% rename from content/posts/2021-02-19-changelogs.md rename to content/posts/2021-02-20-changelogs.md index 57ea55a..e23b5a7 100644 --- a/content/posts/2021-02-19-changelogs.md +++ b/content/posts/2021-02-20-changelogs.md @@ -1,6 +1,6 @@ --- title: Writing good changelogs -date: "2021-02-19" +date: "2021-02-20" --- Today, I finally added a proper changelog to [my current project](https://github.com/garritfra/sabre/blob/master/CHANGELOG.md). My obvious first step was to search the web for `changelog.md`, since that's the naming convention many projects are using for their changelog. I was surprised that I was immediately redirected to "[changelog.md](https://changelog.md)", since it is a valid domain name. This website is a great guide on the essense of a good changelog. This is also where I got most of my findings from. Let me walk you through some of the most important ones: