From 0143e3cddbf8e91eee6b9f17de9cb4c6b8fcc224 Mon Sep 17 00:00:00 2001 From: Dominik Picheta Date: Thu, 7 Sep 2017 22:01:39 +0100 Subject: [PATCH] Updated Creating a release (markdown) --- Creating-a-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Creating-a-release.md b/Creating-a-release.md index 93fd5b8..a6fb508 100644 --- a/Creating-a-release.md +++ b/Creating-a-release.md @@ -42,7 +42,7 @@ PATH=$PATH:$(pwd)/bin - Create a new blog post in `_drafts` titled: `version--released.md` where `` is the version without any dots, e.g. `0180` for `0.18.0`. - When ready to release: - - move the blog post into `_posts` + - move the blog post into `_posts`, making sure to append the current date to its filename: `2017-09-31-title.md`. - modify config.yml's `version` key to the new version - `git commit` - **TIP:** Here is a real-life example of a commit that signifies a release: https://github.com/nim-lang/website/commit/6f95916dee1212dcf5465d74dcff14e01f714503. The draft blog post was created in earlier commits, but hopefully it's pretty easy to figure out how it was made.