From b2fd2618fb3e804dfc7cc018a950698e7c040977 Mon Sep 17 00:00:00 2001 From: nholtware Date: Thu, 5 Nov 2026 01:44:31 -0600 Subject: [PATCH] docs: avoid substituting the variable name in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d8b724..7d6e2e8 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ Logs: one JSON object per line on stdout (`level,time,msg,service,version`, plus ## Using this template -1. **Generate** a repo from this template in Forgejo (public). `${REPO_NAME}` is substituted into `package.json`, this README, `.env.example`, the CI workflow, and the first migration. +1. **Generate** a repo from this template in Forgejo (public). The repo name is substituted into `package.json`, this README, `.env.example`, the CI workflow, and the first migration. 2. **Set 3 Actions secrets** on the new repo: `REGISTRY_USER` (`nholtware`), `REGISTRY_TOKEN` (registry push token), `GITOPS_TOKEN` (ci-bot gitops token). 3. **Add gitops entries**: render `templates/backend/` (see its README) into `manifests//` and add `apps/.yaml` in `nholtware/gitops`. 4. **Push** to `main`. Generating a repo emits no push event, so CI only starts on your first push.