From f7f05e3ec7d7cc984551be6e19c6a762732394f2 Mon Sep 17 00:00:00 2001 From: Stephen Stack Date: Sat, 12 Sep 2026 18:54:40 +0100 Subject: [PATCH] docs: restore master as a mirror of main and say why it stays The repository was renamed from master to main, but older documentation, bookmarks and raw file URLs still point at .../rConfig-templates/master/... Deleting the branch breaks every one of those links, so it has been recreated from main. Documents that it carries no unique work, that nothing should branch from it or merge into it, and how to resync it. Left unsynced it is worse than absent: the old links keep working while quietly serving stale templates. Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index c515888..8dc41b1 100644 --- a/README.md +++ b/README.md @@ -82,6 +82,22 @@ scripts/ Header tooling and the template validator Pro-only material lives under `pro-features/`: the Script Integration Engine templates and example scripts, the SSH private key template, and the xFTP inbound-only template. +## Branches + +`main` is the default branch. Work lands on `dev` and is merged to `main` from there. + +`master` is kept as a mirror of `main`. It carries no unique work and nothing should be branched +from it or merged into it directly. It exists because this repository was renamed from `master` +to `main`, and older documentation, bookmarks and raw file URLs still point at +`.../rConfig-templates/master/...`. Deleting it breaks those links. + +**Keep it in sync when `main` moves**, otherwise those old links silently start serving stale +templates, which is worse than them breaking outright: + +```bash +git push origin origin/main:refs/heads/master +``` + ## Template status Every template declares a status in its header.