AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
docs(release): warn against naming the override marker in prose (#212)
Rufus3f9cadd4c97a
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.ymlindex 2abd5348..5454dfa8 100644--- a/.github/workflows/release-please.yml+++ b/.github/workflows/release-please.yml@@ -17,7 +17,10 @@# bare `Release-As:` line in the description is not enough: footers count only# in the commit's final paragraph, and text appended on merge pushes it out.# The same block with a corrected message fixes a merged PR (e.g. drops a-# wrong `!`). Either is read on the next push to main.+# wrong `!`). Either is read on the next push to main. Write the begin marker+# only once in a description and never in prose: release-please takes the+# text after its first occurrence, so an earlier mention wins and fails to+# parse.## Merging the release PR makes this workflow tag the merge commit `vX.Y.Z`# and create the GitHub Release from the changelog entry. The tag push thendiff --git a/CLAUDE.md b/CLAUDE.mdindex 82433aa2..aa1ae2ca 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -235,7 +235,10 @@ cd evals && python run_evals.py --scenarios scenarios/ --output results/GitHub or the Claude footer appends text after it (#210). It applies to thenext release only. The same block with a corrected message un-marks amerged PR (e.g. drops a wrong `!`). Either takes effect on the next push to- `main`.+ `main`. Write the begin marker only once in a PR description, and never in+ prose: release-please takes the text after its first occurrence, so a+ backticked mention earlier in the body becomes the "message", fails to+ parse, and drops that commit from the release (#210, #211).- PR description is three sections and nothing else: **Problem**, **Approach**,**Checklist** (see `.github/PULL_REQUEST_TEMPLATE.md`). Rationale, reviewfindings and alternatives go in the commit message; open questions go in the