9c573f1e3c
Decisions, environment quirks and pitfalls learned while working on AgentHub (docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account details are left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 lines
763 B
Markdown
13 lines
763 B
Markdown
---
|
|
name: no-git-stash-shared-checkout
|
|
description: Another Claude session may be editing/staging in the same agenthub checkout at the same time — never git stash to compare against HEAD
|
|
metadata:
|
|
type: feedback
|
|
---
|
|
|
|
On 2026-10-06 a parallel session committed v2.5.6 and staged new tmux/package changes in this checkout while I was working; my `git stash`/`stash pop` (to rerun a test on clean code) briefly hid whatever was in the tree.
|
|
|
|
**Why:** stash/pop is checkout-wide; it can swallow or unstage another session's in-flight work.
|
|
|
|
**How to apply:** to test against clean code use `git worktree add /tmp/<x> HEAD` instead. Before reporting, check `git status` for staged changes that are not yours and leave them alone. See [[agenthub-multi-user-goal]].
|