From 7df86414335e451296f568ecf852ba5f9e512ce0 Mon Sep 17 00:00:00 2001
From: Jan Giacomelli <jan.giacomelli@gmail.com>
Date: Fri, 20 Dec 2024 06:58:04 +0100
Subject: [PATCH] Chapter 18 review

---
 chapter_18_second_deploy.asciidoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/chapter_18_second_deploy.asciidoc b/chapter_18_second_deploy.asciidoc
index 02c7db6b..d3599ccb 100644
--- a/chapter_18_second_deploy.asciidoc
+++ b/chapter_18_second_deploy.asciidoc
@@ -191,6 +191,8 @@ NOTE: Some people don't like to use `push -f` and update an existing tag,
     and will instead use some kind of version number to tag their releases.
     Use whatever works for you.
 
+// JAN: I'd advise against using the -f option. If something goes south with the release, it's hard to return to the previous state. I'd suggest simply creating a new tag. Structure that works nicely is <project_name>-<wannabe_iso_date_time>-<latest_commit_sha>-<description>. For example, goat-book-2024-12-20_10_12_13-86fd578r-new-feature-a-added. If there's any issue, it's easy to check out the latest working tag and redeploy.
+
 And on that note, we can wrap up <<part2>>,
 and move on to the more exciting topics that comprise <<part3>>.
 Can't wait!