docs: warn against git operations concurrent with tooling runs#23
Merged
Conversation
Concurrent heavy git activity (a worktree add during an in-flight go test) once corrupted the working repo's state: core.bare flipped and an isolated test fixture's git identity leaked into the local config. The code-side hardening landed in #18; this records the operational guardrail in CONTRIBUTING.md and AGENTS.md, the remaining prevention item. Closes #17 Assisted-by: Claude:claude-fable-5
REPPL
enabled auto-merge (squash)
July 18, 2026 13:58
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.
Why
Concurrent heavy git activity (a
git worktree addduring an in-flightgo test) once corrupted the working repository's state:core.bareflipped and an isolated test fixture's git identity leaked into the local config. The code-side hardening (isolated git env incmd/test helpers) landed in #18; the remaining prevention item from the issue is the operational guardrail.What
CONTRIBUTING.md: a paragraph in "Build, test, and checks" telling contributors to never run git-mutating operations concurrently with a tooling run against this repo.AGENTS.md: the same guardrail for agents, including its practical consequence — no parallel subagents that touch git.Closes #17