From 3013d49fc515c219fa3cb522967d4f81e996f676 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Thu, 3 Feb 2022 17:57:55 +0100 Subject: [PATCH] remove sentence --- docs/maintainers/handbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md index 21d96bac..419e0059 100644 --- a/docs/maintainers/handbook.md +++ b/docs/maintainers/handbook.md @@ -26,7 +26,7 @@ The commands uses for dealing with recipe versioning in `abra` are: - `abra recipe sync`: upgrade the deploy labels to match the new recipe version - `abra recipe release`: publish a git tag for the recipe repo -The `abra` recipe publishing commands have been designed to complement a semi-automatic workflow. If `abra` breaks or doesn't understand what is going on, you can always finish the process manually with a few Git commands and a bit of luck. We designed `abra` to support this way due to the chaotic nature of container publishing versioning schemes. This handbook entry will show you everything you need to know to understand. +The `abra` recipe publishing commands have been designed to complement a semi-automatic workflow. If `abra` breaks or doesn't understand what is going on, you can always finish the process manually with a few Git commands and a bit of luck. We designed `abra` to support this way due to the chaotic nature of container publishing versioning schemes. Let's take a practical example, publishing a new version of [Wordpress](https://git.coopcloud.tech/coop-cloud/wordpress).