From 35717c28952dc4650f1c59137ace116e4f5bf9cd Mon Sep 17 00:00:00 2001 From: Ross Mallory <81823408+rmallorybpc@users.noreply.github.com> Date: Thu, 23 Jun 2022 10:53:09 -0600 Subject: [PATCH] Update README.md --- README.md | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 62869db..40362a6 100644 --- a/README.md +++ b/README.md @@ -180,13 +180,10 @@ You can now [merge](https://docs.github.com/en/get-started/quickstart/github-glo -

Step 5: Finalize the release

 -_Almost there :heart:_ - ### Finalizing releases It's important to be aware of the information what will be visible in that release. In the pre-release, the version and commit messages are visible. @@ -195,7 +192,7 @@ It's important to be aware of the information what will be visible in that relea ### Semantic versioning -Semantic versioning is a formal convention for specifying compatibility. It uses a three-part version number: **major version**; **minor version**; and **patch**. Version numbers convey meaning about the underlying code and what has been modified. For example, versioning could be handled as follows: +Semantic versioning is a formal convention for specifying compatibility. It uses a three-part version number: **major version**; **minor version**; and **patch**. Version numbers convey meaning about the underlying code and what has been modified. For example, versioning could be handled as follows: | Code status | Stage | Rule | Example version | |---|---|---|---| @@ -208,16 +205,16 @@ Check out this article on [Semantic versioning](https://semver.org/) to learn mo ### Finalize the release -Let's now change our recently automated release from _draft_ to _latest release_. +Now let's change our recently automated release from _draft_ to _latest release_. ### :keyboard: Activity: Finalize release -1. In a separate tab, go to the **Releases** page for this repository. +1. In a separate tab, go to the **Releases** page for this repository - To reach this page, click the **Code** tab at the top of your repository. Then, find the navigation bar below the repository description, and click the **Releases** heading link -1. Click the **Edit** button next to your draft release. -1. Ensure the _Target_ branch is set to `main`. -1. Click **Publish release**. -1. Wait about 20 seconds then refresh this page for the next step. +1. Click the **Edit** button next to your draft release +1. Ensure the _Target_ branch is set to `main` +1. Click **Publish release** +1. Wait about 20 seconds then refresh this page for the next step