Repository navigation
contributing: a workspace lives beside the checkout, never under /tmp - #231
Merged
Merged
Conversation
The workspace rule said where to work but not where to put the workspace. A session's scratchpad is under /private/tmp on macOS, where the OS clears files left untouched for a few days; on 2026-10-08 that took `build.zig` and most of `src/` out of a workspace mid-task, and jj's next snapshot recorded the deletions into the working-copy change. The rule moved from one agent's memory into the file the policy says it belongs in. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
CONTRIBUTING.md's workspace rule now says where a workspace goes:../fizzy-<task>, beside the main checkout, and never under/tmpor a session scratchpad.A session's scratchpad is under
/private/tmpon macOS, and the OS clears files there that go untouched for a few days. On 2026-10-08 that tookbuild.zigand most ofsrc/out of a workspace mid-task, and jj's next snapshot recorded the 159 deletions into the working-copy change. Committed changes survived in the main store.The rule had been written to one agent's local memory. This PR moves it to
CONTRIBUTING.md, where #230 says such rules belong.SDK impact
Verified
ci.yml's docs-only path: expectChanges→code=false, the builds skipped, andci-okpassing.Follow-ups
None.
🤖 Generated with Claude Code