From 928e5e2049de10ec6b9bad5fd1ff1559e3035450 Mon Sep 17 00:00:00 2001 From: Christopher Engelhard Date: Fri, 24 Jul 2020 20:44:26 +0200 Subject: [PATCH] fix list indices --- modules/ROOT/pages/publish-rpm-on-copr.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/publish-rpm-on-copr.adoc b/modules/ROOT/pages/publish-rpm-on-copr.adoc index f0f4a43..7815238 100644 --- a/modules/ROOT/pages/publish-rpm-on-copr.adoc +++ b/modules/ROOT/pages/publish-rpm-on-copr.adoc @@ -201,10 +201,10 @@ If you again push the tag to the remote repo, Copr will again automatically trig == Release procedure in brief From now on, updating your software in the Copr repository is as simple as -0. Commit all changes for your new version. -1. Perform a test build using `tito build --test` -2. Tag the release with `tito tag` (add `--use-version` if necessary) -3. Push the tag to your git repo using `git push --follow-tags` +1. Commit all changes for your new version. +2. Perform a test build using `tito build --test` +3. Tag the release with `tito tag` (add `--use-version` if necessary) +4. Push the tag to your git repo using `git push --follow-tags` and Copr will take care of the rest.