ensure-working-branch: scope stash-freshness check to current branch - #87
Open
jodavis-claude wants to merge 1 commit into
Open
ensure-working-branch: scope stash-freshness check to current branch#87jodavis-claude wants to merge 1 commit into
jodavis-claude wants to merge 1 commit into
Conversation
git stash refs are shared repo-wide across every worktree, not scoped per-worktree. Any leftover stash entry from an unrelated past or concurrent session was hard-stopping every new task's freshness check, even when it had nothing to do with that task's branch. Filter to entries referencing the current branch instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
build-and-test: Python test resultsStatus: ✅ Passed Test log |
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
2 participants
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.
Summary
git stashrefs are shared repo-wide across every worktree, not scoped per-worktreeensure-working-branchstep 1 was failing on any non-emptygit stash list, even entries left behind by unrelated past/concurrent sessions on other branchesContext
Found while running
concurrent-orchestratefor ADR-341 in AdaptiveRemote: the check hard-stopped on 6 stale stash entries from unrelated prior sessions, none belonging to the task's own branch.Test plan
Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com