From 0548e14db944dd5fcd1065a19857d6d924162082 Mon Sep 17 00:00:00 2001 From: jonasbn Date: Fri, 31 Jul 2026 12:46:39 +0200 Subject: [PATCH] Document YAML-validity verification and open-branch push gotchas Two learnings from the 0.64.0 release cycle: verify reviewer claims about YAML validity with an actual parser rather than trusting them, and expect open PR branches to sometimes receive direct pushes from the user outside the session. Co-Authored-By: Claude Sonnet 5 --- CLAUDE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 10ab6fe3..3707bf8a 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -143,3 +143,8 @@ The Docker image is published via the `docker-build.yml` workflow on push to `ma ## README YAML Examples - Inputs under `with:` in workflow YAML examples must be indented 2 spaces relative to `with:`. This has been a recurring source of invalid examples. +- Don't trust a reviewer's (e.g. Copilot's) "this is invalid YAML" claim at face value — verify with `python3 -c "import yaml; yaml.safe_load(open('README.md').read())"` on the extracted block. Same-indentation block sequences (list items aligned with their parent key) are valid YAML even though they look wrong; the real issue is usually inconsistency with this file's convention, not invalidity. + +## Working on Open Branches + +- Branches behind open PRs may receive direct pushes from the user (e.g. resolving a merge conflict via the GitHub UI) while a session is in progress. A local `git push` can be rejected as a result — `git fetch` and merge (don't force-push) before retrying.