|
|
@@ -106,7 +106,7 @@ Branch version names should only target major/minor releases, not the patch of a
|
|
|
When it's time to cut a new version for the wiki, the process is as follows.
|
|
|
|
|
|
. Create and checkout a new branch that matches the *current version* of the wiki. If the current version (HEAD) is targeting version 3.3 in the `antora.yml` for example, you would name the new branch `v3.3`. Thereby preserving the current master branch content.
|
|
|
-. We do not want the Antora `.cache` to be versioned so you need to delete it from the new version branch.
|
|
|
+. We do not want the Antora `.cache` to be versioned so you need to delete it from the new version branch if it has been commited to the repo.
|
|
|
. Push the branch to the repository.
|
|
|
. Switch to the `master` branch and edit these files:
|
|
|
.. Add the newly created branch to the `branches:` array in `wiki-playbook.yml`.
|
mitm001