docs: branch off development, with a stacking exception
Working branches start from the latest origin/development. Exception: work that depends on an unmerged feature branch may stack on it — merge the base PR first, then rebase the stacked branch onto development before opening its pull request. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f6zfWDT1v5TeSpA29rEyx
Claude committed
Jul 2, 2026 at 09:05 UTC
4eeda0f36fd0de5a09fd59200ef85f5973e11c88
1 file changed
+7
CLAUDE.md
+7
@@ -28,6 +28,13 @@ a task, ticket, or session id (not `feature/task-q003hm`).
28
**IMPORTANT — pull request target:** Always open pull requests against the `development` branch,
29
never `main`. `main` is release-only; `development` is where day-to-day work integrates.
30
31
+**IMPORTANT — branch off `development`:** Start every working branch from the latest
32
+`origin/development`. Exception: when new work *depends on* a feature branch that has not merged
33
+yet (e.g. it builds on tools or APIs that branch introduces), it may be stacked on top of that
34
+branch instead. When stacking: merge the base PR into `development` first, then rebase the
35
+stacked branch onto `development` before opening its pull request, so each PR shows only its own
36
+commits.
37
+
38
**IMPORTANT — run CI before pushing:** Run the full CI gate locally and confirm it is green
39
*before* pushing a branch or opening a pull request — never push work that fails these:
40