From ba6514b626c349c66237d74b9f68e6bd290cd00c Mon Sep 17 00:00:00 2001 From: "Robert J. Lang" Date: Thu, 2 Jan 2025 09:31:34 -0800 Subject: [PATCH] Fix typo in README file. --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index b0b3c58..ac5c6ec 100644 --- a/README.md +++ b/README.md @@ -179,27 +179,27 @@ When you are ready: Releases -------- -The module, theme and layout releases on Backdropcms.org rely on GitHub -releases. Before creating a GitHub release, you must first add git tag. -The format for the tag should be "1.x-1.0.0". "1.x-1.0.0-alpha1" or -"1.x-1.0.0--beta1" can also be used to indicate a project is not yet +The module, theme and layout releases on Backdropcms.org rely on GitHub +releases. Before creating a GitHub release, you must first add git tag. +The format for the tag should be "1.x-1.0.0". "1.x-1.0.0-alpha1" or +"1.x-1.0.0-beta1" can also be used to indicate a project is not yet stable and should be used with caution. The most common order of operations is as follows: - 1. Add a tag using `git tag 1.x-1.0.0` + 1. Add a tag using `git tag 1.x-1.0.0` 1. Push the tag up to the contrib repository. - 1. Visit the page for the tag in GitHub and + 1. Visit the page for the tag in GitHub and [create a release from that page](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). 1. Wait. This process can take anywhere 5 seconds to 5 minutes. 1. Refresh the GitHub release page. You should see a "Download XYZ" link appear. If successful, your project should appear on the [modules](https://backdropcms.org/modules), -[themes](https://backdropcms.org/themes) or [layouts](https://backdropcms.org/layouts) +[themes](https://backdropcms.org/themes) or [layouts](https://backdropcms.org/layouts) listing pages on BackdropCMS.org. If there was an error during the packaging process, an error message from the -packager will be attached instead. +packager will be attached instead. Security Releases