From e64d07cb49dd3313eb8595935777f31fdfb2f373 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 26 May 2026 07:15:38 +0000 Subject: Clarify merge policy: merge when done, not at session end https://claude.ai/code/session_01YUbuZNDAoLea4cf9UGQ9qn --- .agent/preferences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.agent/preferences.md b/.agent/preferences.md index f703998..9ae92fa 100644 --- a/.agent/preferences.md +++ b/.agent/preferences.md @@ -15,7 +15,7 @@ Living record of user preferences for the Nav project. ## 2. Merge Policy — NON-NEGOTIABLE - **Merge to `main` after every complete unit of work.** Nothing counts until it lands on `main` — that's when the user can test it. Don't batch up multiple tasks across a session and merge at the end. Each self-contained piece (a feature, a bug fix, a redesign) merges to `main` as soon as it's working and tested. - Feature branches are short-lived and merge-forward aggressively. Push the branch, then immediately merge it to `main` and push `main`. -- **Never leave a session with completed work sitting on a feature branch.** +- **Merge immediately when a task is done — not at session end, not during cleanup.** "Prep for new session" should never be the moment work first lands on main. ## 3. Repository Conventions — NON-NEGOTIABLE - **Default branch is `main`.** Always has been, always will be. -- cgit v1.2.3