From a8a8cc8b0fe44ea1202962aab108a771496143de Mon Sep 17 00:00:00 2001
From: Lee Watson <lee.watson@netgo.de>
Date: Thu, 27 Feb 2025 14:00:45 +0000
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 771dd3a..d24cf09 100644
--- a/README.md
+++ b/README.md
@@ -13,8 +13,9 @@ Roles:
   * E.g. look up in in [verify/.sops.yaml](verify/.sops.yaml)
 
 ## 1a. Onboarding: [New User]: create and add a gpg key
-- create a branch titled `add_pubkey_<firstname>-<lastname>` <!-- Review from Bas: Please make sure it's clear to the user that you mean this repo. -->
-  - e.g. `git branch add_pubkey_test-user`
+- Within this repository, create a branch titled `add_pubkey_[firstname]-[lastname]`. <!-- NOTE: Validation Hack: User will not be able to mistakenly create this literal branch, as the unpermitted chars '[' will prevent the branch from being created: "Branch name cannot contain '['" as per https://git-scm.com/docs/git-check-ref-format. I.e. it's a dirty hack to get some server-side(?) validation ;-) --> 
+  - Web: e.g. The following link can be used to create a branch: [https://git.dev-at.de/smardigo-hetzner/communication-keys/-/branches/new?branch_name=add_pubkey_[firstname]-[lastname]]()
+  - CLI: e.g. `git branch add_pubkey_[firstname]-[lastname]`
   - Note: no strict naming convention for the branch, it's strictly a Human-in-the-Loop process
 - please follow steps 1-13 at the following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
   - CAVEAT: step 14 is not necessary, as it is specific to a GitHub account