Repository navigation
fix: use full clone in v1 branch update workflow - #57
Closed
tend-agent wants to merge 1 commit into
Closed
tend-agent wants to merge 1 commit into
tend-agent wants to merge 1 commit into
Conversation
The shallow clone (default fetch-depth: 1) causes git push to fail with "remote contains work that you do not have locally" because the local repo can't prove the fast-forward to the remote without full history. This broke the v1 auto-update after PR #55 merged, keeping v1 stuck at fbf397e while main advanced. As a result, the compat fix in PR #54 cannot reach adopters even after merge. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Mar 25, 2026
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
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
fetch-depth: 0to the checkout step in the v1 branch update workflow so git has full history to prove the fast-forward pushRoot cause
The "Update action branch" workflow uses a shallow clone (default
fetch-depth: 1), which only has the tip commit. When pushingHEAD:refs/heads/v1, git cannot prove to the remote that the push is a fast-forward without the common ancestor in local history. The remote rejects with:This broke the v1 auto-update when PR #55 merged, keeping
v1stuck atfbf397ewhile main advanced to9466b6a. The compat fix (PR #54) — which unblocks all adopter review runs — cannot reach adopters until v1 is updated.Evidence
git push origin HEAD:refs/heads/v1rejectedtend-reviewruns on adopter repos (e.g. max-sixty/worktrunk) continue failing withUnknown skill: tend:tend-reviewbecause v1 still points to pre-compat codeGate assessment
Test plan
🤖 Generated with Claude Code