Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chapter 18 review #336

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Chapter 18 review #336

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions chapter_18_second_deploy.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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!
Expand Down
Loading