From 40660c6b3390f6477ecd372c53f23e0bcb5f6ab8 Mon Sep 17 00:00:00 2001
From: TC <tc@geekministry.org>
Date: Fri, 5 Apr 2024 03:20:34 +0000
Subject: [PATCH] Added instructions for, and simultaneously testing, [ci skip]

---
 RELEASING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index 5b5085a6..7948a368 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -20,13 +20,13 @@ Releases happen via a CI/CD pipeline. The release process flows as follows:
 
     2.1 Update your local copy of `main` to mirror the newly merged upstream `main`
 
-    2.2 Ensure the [CHANGELOG](./CHANGELOG.md) is updated
+    2.2 Ensure the [CHANGELOG](./CHANGELOG.md) is updated. Include `[ci skip]` in the commit message so that the testing pipeline is skipped.
 
     2.3 Activate your bumpversion Python venv (see bumpversion setup section for details)
 
     2.4 Execute version_bump.sh with the appropriate parameter (patch, minor, or major). This results in all version entries being updated and a matching git tag created locally.
 
-    2.5 Add all changes `git add *`
+    2.5 Add all changes `git add .`
 
     2.6 Git commit the changes with the following message: `Version update: v{current_version} → v{new_version}`